hpwdurham.com - robtex.com
hpwdurham.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 66.192.167.187🇺🇸 AS354966.192.0.0/14 | ||||||
| PTR | mail2.hpw.com | ||||||
| NS | mns01.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2143::1f🇺🇸 GODADDY-DNS2603:5:2140::/44 | ||||||
| PTR | mns01.domaincontrol.com | ||||||
| A | 97.74.100.31🇺🇸 GODADDY-DNS97.74.100.0/23 | ||||||
| PTR | ns59.domaincontrol.com | ||||||
| NS | mns02.domaincontrol.com | ||||||
| A | 2603:5:2243::1f🇺🇸 GODADDY-DNS2603:5:2240::/44 | ||||||
| PTR | mns02.domaincontrol.com | ||||||
| A | 173.201.68.31🇺🇸 GODADDY-DNS173.201.68.0/23 | ||||||
| PTR | ns60.domaincontrol.com | ||||||
| SOA | mns01.domaincontrol.comdns@jomax.net 2016-03-22 #0 | ||||||
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=1785195232 | ||||||
Same first word
hpwdurham.com |
DNS History
5 records (3 active, 2 former)
●NSmns01.domaincontrol.com2015-06-19 → 2026-07-27 · 3 obs
● 2015-06-19 00:33:46
● 2026-07-27 23:53:30
●NSmns02.domaincontrol.com2015-06-19 → 2026-07-27 · 3 obs
● 2015-06-19 00:33:46
● 2026-07-27 23:53:30
○NSns2.netsolus.com2008-03-13 → 2008-03-13 · 3 obs
○ 2015-06-19 00:33:46
○ 2026-07-27 23:53:30
○NSns3.netsolus.com2008-03-13 → 2008-03-13 · 3 obs
○ 2015-06-19 00:33:46
○ 2026-07-27 23:53:30
●A66.192.167.1872015-06-19 → 2026-07-27 · 3 obs
● 2015-06-19 00:33:46
● 2026-07-27 23:53: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... | - |
| hpwdurham.com | mns01.domaincontrol.com, mns02.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.100.31
NS records: mns01.domaincontrol.com, mns02.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for hpwdurham.com (unsigned zone)
⏱️ Timing
Total: 115ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.192.167.187 |
| NS | 2 | mns01.domaincontrol.com, mns02.domaincontrol.com |
| SOA | 1 | mns01.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (mns01.domaincontrol.com, mns01.domaincontrol.com, mns02.domaincontrol.com...)
Analysis
IP Addresses
hpwdurham.com resolves to just one IP address, 66.192.167.187.
Name Servers
hpwdurham.com is delegated to two name servers: mns01.domaincontrol.com and mns02.domaincontrol.com.
hpwdurham.com shares its NS records with other domains, for example europartners.com.pa, etmtrtshom.com, compedia.co.il and two others.
hpwdurham.com has at least partial name server overlap with other domains, such as sergiomartinez.mx, texomacars.com, transitchekcard.com and two others.
It is common to see these name servers used together with name servers mns1.secureserver.net and mns2.secureserver.net.
mns01.domaincontrol.com and mns02.domaincontrol.com each resolve to two IP addresses: mns01.domaincontrol.com points to 97.74.100.31 and 2603:5:2143::1f, while mns02.domaincontrol.com points to 173.201.68.31 and 2603:5:2243::1f.