terrorevent.com - robtex.com
terrorevent.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=1774973312 | ||||||
Same first word
terrorevent.com |
DNS History
9 records (4 active, 5 former)
●NSns-cloud-a1.googledomains.com2026-03-31 → 2026-03-31 · 2 obs
● 2026-03-31 16:18:24
●NSns-cloud-a2.googledomains.com2026-03-31 → 2026-03-31 · 2 obs
● 2026-03-31 16:18:24
●NSns-cloud-a3.googledomains.com2026-03-31 → 2026-03-31 · 2 obs
● 2026-03-31 16:18:24
●NSns-cloud-a4.googledomains.com2026-03-31 → 2026-03-31 · 2 obs
● 2026-03-31 16:18:24
○NSns49.domaincontrol.com2015-07-12 → 2016-02-29 · 4 obs
● 2016-02-29 17:56:24
○ 2016-06-17 20:10:06
○ 2026-03-31 16:18:24
○NSns50.domaincontrol.com2015-07-12 → 2016-02-29 · 4 obs
● 2016-02-29 17:56:24
○ 2016-06-17 20:10:06
○ 2026-03-31 16:18:24
○MXmailstore1.secureserver.net2015-07-12 → 2016-02-29 · 4 obs
● 2016-02-29 17:56:24
○ 2016-06-17 20:10:06
○ 2026-03-31 16:18:24
○MXsmtp.secureserver.net2015-07-12 → 2016-02-29 · 4 obs
● 2016-02-29 17:56:24
○ 2016-06-17 20:10:06
○ 2026-03-31 16:18:24
○A50.63.202.422015-07-12 → 2016-02-29 · 4 obs
● 2016-02-29 17:56:24
○ 2016-06-17 20:10:06
○ 2026-03-31 16:18:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, c.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net... | - |
| terrorevent.com | ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com | 8 records |
✅ Authoritative Response
Server:216.239.36.106
NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for terrorevent.com (unsigned zone)
⏱️ Timing
Total: 286ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-cloud-a4.googledomains.com, ns-cloud-a3.googledomains.com... |
| SOA | 1 | ns-cloud-a1.googledomains.com cloud-dns- |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)
Analysis
Name Servers
terrorevent.com's delegation is handled by four name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.
terrorevent.com partially shares name servers with other domains; examples include tyehenderson.com, tonyventresca.com, kawaiibabystore.com, landbanktrust.com and deadstockgreen.com.
Host names with two IPs:
ns-cloud-a1.googledomains.com points to 2001:4860:4802:32::6a and 216.239.32.106
ns-cloud-a2.googledomains.com points to 2001:4860:4802:34::6a and 216.239.34.106
ns-cloud-a3.googledomains.com points to 2001:4860:4802:36::6a and 216.239.36.106
ns-cloud-a4.googledomains.com points to 2001:4860:4802:38::6a and 216.239.38.106