triggerwarningpod.com - dns.ninja
triggerwarningpod.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1792633851 | ||||||
Same first word
triggerwarningpod.com |
Previous names
Next names
DNS History
9 records (9 active, 0 former)
●NSns01.domaincontrol.com2026-09-05 → 2026-10-22 · 2 obs
● 2026-10-22 02:11:40
●NSns02.domaincontrol.com2026-09-05 → 2026-10-22 · 2 obs
● 2026-10-22 02:11:40
●MXalt1.aspmx.l.google.com2026-09-05 → 2026-10-22 · 2 obs
● 2026-10-22 02:11:40
●MXalt2.aspmx.l.google.com2026-09-05 → 2026-10-22 · 2 obs
● 2026-10-22 02:11:40
●MXalt3.aspmx.l.google.com2026-09-05 → 2026-10-22 · 2 obs
● 2026-10-22 02:11:40
●MXalt4.aspmx.l.google.com2026-09-05 → 2026-10-22 · 2 obs
● 2026-10-22 02:11:40
●MXaspmx.l.google.com2026-09-05 → 2026-10-22 · 2 obs
● 2026-10-22 02:11:40
●A13.248.243.52026-09-05 → 2026-10-22 · 2 obs
● 2026-10-22 02:11:40
●A76.223.105.2302026-09-05 → 2026-10-22 · 2 obs
● 2026-10-22 02:11:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| triggerwarningpod.com | ns01.domaincontrol.com, ns02.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.68.1
NS records: ns01.domaincontrol.com, ns02.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for triggerwarningpod.com (unsigned zone)
⏱️ Timing
Total: 1337ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 76.223.105.230, 13.248.243.5 |
| NS | 2 | ns01.domaincontrol.com, ns02.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 include:dc-aa8e722993._spfm.trigg |
| SOA | 1 | ns01.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns01.domaincontrol.com, ns01.domaincontrol.com, ns02.domaincontrol.com...)
Analysis
IP Addresses
triggerwarningpod.com resolves to the IP addresses 13.248.243.5 and 76.223.105.230
Additional host names — alessiacampagna.com.au, amanicuristsparlour.com, hausofchic.com and two others — share IP numbers with triggerwarningpod.com.
Name Servers
DNS delegation for triggerwarningpod.com points to two name servers: ns01.domaincontrol.com and ns02.domaincontrol.com.
triggerwarningpod.com shares its name server setup with other domains, including 26milesatsea.com, rroyse.com, breethe.com.au and two others.
ns01.domaincontrol.com directs to 97.74.100.1 and 2603:5:2140::1. ns02.domaincontrol.com directs to 173.201.68.1 and 2603:5:2240::1. Each host name carries two IP addresses.
Mail Servers
triggerwarningpod.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
triggerwarningpod.com shares mail servers — at least in part — with other domains, including beijingvivietours.com, wherethemoonmeetsthesea.com, zenprofinanciero.com and two others.
These mail servers are frequently used alongside the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and aspmx2.googlemail.com, plus two others.
Host names with two IP numbers:
aspmx.l.google.com has two IP addresses: 172.217.75.26 and 2607:f8b0:4023:200d::1a.
alt1.aspmx.l.google.com has two IP addresses: 172.253.145.26 and 2607:f8b0:4023:3003::1b.
alt2.aspmx.l.google.com has two IP addresses: 172.253.135.27 and 2607:f8b0:4023:1015::1b.
alt3.aspmx.l.google.com has two IP addresses: 172.253.152.26 and 2a00:1450:4010:c22::1a.
alt4.aspmx.l.google.com has two IP addresses: 192.179.20.27 and 2404:6800:4000:1027::1b.