metroanswering.com - robtex.com
metroanswering.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.33.251.168🇺🇸 Amazon3.33.240.0/20 | ||||||
| PTR | aec037177372cc6cd.awsglobalaccelerator.com | ||||||
| A | 15.197.225.128🇺🇸 Amazon15.197.224.0/20 | ||||||
| NS | ns19.domaincontrol.com ⭐ | ||||||
| A | 2603:5:21d0::a🇺🇸 GODADDY-DNS2603:5:21d0::/44 | ||||||
| PTR | ns19.domaincontrol.com | ||||||
| A | 97.74.109.10🇺🇸 GODADDY-DNS97.74.108.0/23 | ||||||
| PTR | ns19.domaincontrol.com | ||||||
| NS | ns20.domaincontrol.com | ||||||
| A | 2603:5:22d0::a🇺🇸 GODADDY-DNS2603:5:22d0::/44 | ||||||
| PTR | ns20.domaincontrol.com | ||||||
| A | 173.201.77.10🇺🇸 GODADDY-DNS173.201.76.0/23 | ||||||
| PTR | ns20.domaincontrol.com | ||||||
| SOA | ns19.domaincontrol.comdns@jomax.net 2026-07-12 #3 | ||||||
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=1785916089 | ||||||
Previously MX for
metroanswering.com |
Same first word
metroanswering.com |
DNS History
22 records (4 active, 18 former)
○NSns1.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSns1.metroanswering.com2015-05-30 → 2015-05-30 · 3 obs
● 2015-05-30 09:03:06
○ 2015-11-02 03:13:56
○ 2026-08-05 07:55:30
○ 2015-11-02 03:13:56
○ 2026-08-05 07:55:30
●NSns19.domaincontrol.com2026-03-29 → 2026-08-05 · 3 obs
○ 2017-06-09 10:13:44
● 2026-03-29 10:58:02
● 2026-08-05 07:55:30
● 2026-03-29 10:58:02
● 2026-08-05 07:55:30
○NSns2.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSns2.metroanswering.com2015-05-30 → 2015-05-30 · 3 obs
● 2015-05-30 09:03:06
○ 2015-11-02 03:13:56
○ 2026-08-05 07:55:30
○ 2015-11-02 03:13:56
○ 2026-08-05 07:55:30
●NSns20.domaincontrol.com2026-03-29 → 2026-08-05 · 3 obs
○ 2017-06-09 10:13:44
● 2026-03-29 10:58:02
● 2026-08-05 07:55:30
● 2026-03-29 10:58:02
● 2026-08-05 07:55:30
○NSns3.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSns4.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSpns1.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSpns10.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSpns2.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSpns3.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSpns4.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSpns5.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSpns6.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSpns7.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSpns8.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○NSpns9.cloudns.net2015-11-02 → 2017-06-09 · 5 obs
○ 2015-05-30 09:03:06
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2015-11-02 03:13:56
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○MXmetroanswering.com2015-05-30 → 2017-06-09 · 4 obs
● 2015-05-30 09:03:06
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
○A12.146.135.1322015-05-30 → 2017-06-09 · 4 obs
● 2015-05-30 09:03:06
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
● 2017-06-09 10:13:44
○ 2026-03-29 10:58:02
○ 2026-08-05 07:55:30
●A15.197.225.1282026-03-29 → 2026-08-05 · 3 obs
○ 2017-06-09 10:13:44
● 2026-03-29 10:58:02
● 2026-08-05 07:55:30
● 2026-03-29 10:58:02
● 2026-08-05 07:55:30
●A3.33.251.1682026-03-29 → 2026-08-05 · 3 obs
○ 2017-06-09 10:13:44
● 2026-03-29 10:58:02
● 2026-08-05 07:55:30
● 2026-03-29 10:58:02
● 2026-08-05 07:55:30
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| metroanswering.com | ns19.domaincontrol.com, ns20.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.77.10
NS records: ns19.domaincontrol.com, ns20.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for metroanswering.com (unsigned zone)
⏱️ Timing
Total: 109ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns20.domaincontrol.com, ns19.domaincontrol.com |
| SOA | 1 | ns19.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns19.domaincontrol.com, ns19.domaincontrol.com, ns20.domaincontrol.com...)
Analysis
IP Addresses
metroanswering.com has two IP addresses: 3.33.251.168 and 15.197.225.128
johnleejohnlee.com, spankingnet.com, bstix.com plus two other host names have IP numbers in common with metroanswering.com.
Name Servers
metroanswering.com uses two name servers for its delegation: ns19.domaincontrol.com and ns20.domaincontrol.com.
The name server configuration of metroanswering.com is shared with other domains, for instance eventchain.io, cetinel.info, petcontract.com and two others.
The two host names ns19.domaincontrol.com and ns20.domaincontrol.com each have a pair of IP addresses: ns19.domaincontrol.com has 97.74.109.10 and 2603:5:21d0::a, and ns20.domaincontrol.com has 173.201.77.10 and 2603:5:22d0::a.