ticketnegligence.com - robtex.com
ticketnegligence.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=1778353081 | ||||||
Same first word
ticketnegligence.com |
DNS History
12 records (12 active, 0 former)
●NSns1.dns-redirect.com2026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●NSns2.dns-redirect.com2026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●A195.201.128.1792026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●A2600:9000:a612:55d9:1b82:e963:5969:d2c72026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●A2a01:4f8:1c1e:d6f1::12026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●A2a01:4ff:1f0:dd50::12026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●A2a01:4ff:f0:5f41::12026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●A46.62.237.1382026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●A5.161.230.872026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●A5.161.47.862026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●A5.78.156.592026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
●A76.223.91.202026-02-23 → 2026-05-09 · 2 obs
● 2026-05-09 19:25:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ticketnegligence.com | ns1.dns-redirect.com, ns2.dns-redirect.com | 5 records |
✅ Authoritative Response
Server:166.117.68.124
NS records: ns1.dns-redirect.com, ns2.dns-redirect.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ticketnegligence.com (unsigned zone)
⏱️ Timing
Total: 419ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 6 | 46.62.237.138, 5.161.230.87... |
| AAAA | 4 | 2600:9000:a612:55d9:1b82:e963:5969:d2c7, 2a01:4ff:1f0:dd50::1... |
| NS | 2 | ns1.dns-redirect.com, ns2.dns-redirect.com |
| TXT | 2 | 95b3a950-315c-45b8-937a-b865ebeb043a, afternic-verification-aGHTsEA2nLa7KRqzmJ |
| SOA | 1 | ns1.dns-redirect.com admin.redirhub.com |
📌 Glue Records Collected
Total: 5
Out-of-bailiwick: 5 (ns1.dns-redirect.com, ns1.dns-redirect.com, ns1.dns-redirect.com...)
Analysis
IP Addresses
Ten IP numbers are pointed to by ticketnegligence.com: 2600:9000:a612:55d9:1b82:e963:5969:d2c7, 2a01:4f8:1c1e:d6f1::1, 2a01:4ff:f0:5f41::1, 2a01:4ff:1f0:dd50::1, 5.78.156.59, 5.161.47.86, 5.161.230.87, 46.62.237.138, 76.223.91.20 and 195.201.128.179.
Other host names, for instance abstract.pizza, wolfe.systems, donotjoin.com, www.ignouportal.com and femalediet.com share IP numbers with ticketnegligence.com.
Name Servers
Two name servers ns1.dns-redirect.com and ns2.dns-redirect.com are delegated to ticketnegligence.com.
ticketnegligence.com uses the same name server configuration as other domains, such as millidgevillemedicalclinic.com, 21p-specials-choker.lili.network, totalnetworks.co.uk, microinterior.com and mx.lizderoche.com.
Three IP numbers: ns1.dns-redirect.com correspond to 5.161.47.86, 5.161.230.87 and 195.201.128.179.
Two IP numbers: ns2.dns-redirect.com correspond to 76.223.91.20 and 166.117.68.124.