antivegas.com - robtex.com
antivegas.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=1786122814 | ||||||
Same first word
antivegas.com |
Similar names
DNS History
11 records (6 active, 5 former)
○NSdns.pool.com2015-07-05 → 2017-07-09 · 4 obs
● 2017-07-09 21:11:46
○ 2019-06-10 14:55:10
○ 2026-08-07 17:29:06
○NSdns2.pool.com2015-07-05 → 2017-07-09 · 4 obs
● 2017-07-09 21:11:46
○ 2019-06-10 14:55:10
○ 2026-08-07 17:29:06
○NSnoc.pool.com2015-07-05 → 2017-07-09 · 4 obs
● 2017-07-09 21:11:46
○ 2019-06-10 14:55:10
○ 2026-08-07 17:29:06
●NSns1.name.com2026-04-08 → 2026-08-07 · 3 obs
● 2026-04-08 04:28:22
● 2026-08-07 17:29:06
●NSns1lmy.name.com2019-06-10 → 2026-08-07 · 3 obs
● 2019-06-10 14:55:10
● 2026-08-07 17:29:06
●NSns2bkr.name.com2019-06-10 → 2026-08-07 · 3 obs
● 2019-06-10 14:55:10
● 2026-08-07 17:29:06
●NSns3gmt.name.com2019-06-10 → 2026-08-07 · 3 obs
● 2019-06-10 14:55:10
● 2026-08-07 17:29:06
●NSns4fpy.name.com2019-06-10 → 2026-08-07 · 3 obs
● 2019-06-10 14:55:10
● 2026-08-07 17:29:06
○A195.20.43.1202015-07-05 → 2015-07-05 · 3 obs
○ 2017-07-09 21:11:46
○ 2026-08-07 17:29:06
○A66.228.63.512015-07-05 → 2017-07-09 · 4 obs
● 2017-07-09 21:11:46
○ 2019-06-10 14:55:10
○ 2026-08-07 17:29:06
●A91.195.240.942019-06-10 → 2026-08-07 · 3 obs
● 2019-06-10 14:55:10
● 2026-08-07 17:29:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, k.gtld-servers.net, j.gtld-servers.net, g.gtld-servers.net... | - |
| antivegas.com | ns1lmy.name.com, ns2bkr.name.com, ns3gmt.name.com, ns4fpy.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1lmy.name.com, ns2bkr.name.com, ns3gmt.name.com, ns4fpy.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for antivegas.com (unsigned zone)
⏱️ Timing
Total: 366ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 91.195.240.94 |
| NS | 4 | ns1lmy.name.com, ns2bkr.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1lmy.name.com, ns1lmy.name.com, ns2bkr.name.com...)
Analysis
IP Addresses
antivegas.com points to a single IP number: 91.195.240.94.
Additional host names — infotoast.com, sponge(0x626f6f62)s.com, agcallback.kb7799.com and two others — share IP numbers with antivegas.com.
Name Servers
Delegation for antivegas.com is to five name servers: ns1.name.com, ns1lmy.name.com, ns2bkr.name.com and two others.
The name servers of antivegas.com overlap at least partially with those of other domains — among them glattorganics.com, (0x616e616c)conda.com, oatwinema.com and two more.
These name servers commonly appear in delegations together with ns4fpy.name.com, ns3gmt.name.com, ns1kpv.name.com and 7 other.
Host names with two IP numbers:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1lmy.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2bkr.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3gmt.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4fpy.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1lmy.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1lmy.name.com resolve to 163.114.216.17 IP addresses each.