adr-resolve.com - robtex.com
adr-resolve.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.veraserve1.com ⚠️ Not in zone NS records | ||||||
| NS | ns2.veraserve1.com ⚠️ Not in zone NS records | ||||||
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=1778592316 | ||||||
Previously MX for
adr-resolve.com |
Same first word
adr-resolve.com |
Similar names
DNS History
7 records (2 active, 5 former)
○NSns1.veraserve.com2016-08-08 → 2017-12-14 · 5 obs
○ 2016-03-26 04:47:36
● 2016-08-08 21:59:36
● 2017-12-14 01:56:54
○ 2026-03-26 05:04:46
○ 2026-05-12 13:46:12
● 2016-08-08 21:59:36
● 2017-12-14 01:56:54
○ 2026-03-26 05:04:46
○ 2026-05-12 13:46:12
●NSns1.veraserve1.com2015-10-16 → 2026-05-12 · 6 obs
● 2015-10-16 10:33:36
● 2016-03-26 04:47:36
○ 2016-08-08 21:59:36
○ 2017-12-14 01:56:54
● 2026-03-26 05:04:46
● 2026-05-12 13:46:12
● 2016-03-26 04:47:36
○ 2016-08-08 21:59:36
○ 2017-12-14 01:56:54
● 2026-03-26 05:04:46
● 2026-05-12 13:46:12
○NSns2.veraserve.com2016-08-08 → 2017-12-14 · 5 obs
○ 2016-03-26 04:47:36
● 2016-08-08 21:59:36
● 2017-12-14 01:56:54
○ 2026-03-26 05:04:46
○ 2026-05-12 13:46:12
● 2016-08-08 21:59:36
● 2017-12-14 01:56:54
○ 2026-03-26 05:04:46
○ 2026-05-12 13:46:12
●NSns2.veraserve1.com2015-10-16 → 2026-05-12 · 6 obs
● 2015-10-16 10:33:36
● 2016-03-26 04:47:36
○ 2016-08-08 21:59:36
○ 2017-12-14 01:56:54
● 2026-03-26 05:04:46
● 2026-05-12 13:46:12
● 2016-03-26 04:47:36
○ 2016-08-08 21:59:36
○ 2017-12-14 01:56:54
● 2026-03-26 05:04:46
● 2026-05-12 13:46:12
○MXadr-resolve.com2015-10-16 → 2017-12-14 · 4 obs
● 2015-10-16 10:33:36
● 2017-12-14 01:56:54
○ 2026-03-26 05:04:46
○ 2026-05-12 13:46:12
● 2017-12-14 01:56:54
○ 2026-03-26 05:04:46
○ 2026-05-12 13:46:12
○A64.50.180.1202016-08-08 → 2017-12-14 · 5 obs
○ 2016-03-26 04:47:36
● 2016-08-08 21:59:36
● 2017-12-14 01:56:54
○ 2026-03-26 05:04:46
○ 2026-05-12 13:46:12
● 2016-08-08 21:59:36
● 2017-12-14 01:56:54
○ 2026-03-26 05:04:46
○ 2026-05-12 13:46:12
○A74.50.23.1402015-10-16 → 2016-03-26 · 4 obs
● 2015-10-16 10:33:36
● 2016-03-26 04:47:36
○ 2016-08-08 21:59:36
○ 2026-05-12 13:46:12
● 2016-03-26 04:47:36
○ 2016-08-08 21:59:36
○ 2026-05-12 13:46:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| adr-resolve.com | ns1.veraserve1.com, ns2.veraserve1.com | 2 records |
✅ Authoritative Response
Server:172.105.254.201
NS records: ns1.veraserve1.com, ns2.veraserve1.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for adr-resolve.com (unsigned zone)
⏱️ Timing
Total: 564ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.veraserve1.com, ns2.veraserve1.com)
Analysis
Name Servers
adr-resolve.com is delegated to two name servers: ns1.veraserve1.com and ns2.veraserve1.com.