whitehatsec.net - robtex.com
whitehatsec.net
net
| 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=1785390287 | ||||||
Same first word
whitehatsec.com |
whitehatsec.eu |
whitehatsec.us |
whitehatsec.nu |
whitehatsec.biz |
whitehatsec.de |
whitehatsec.info |
whitehatsec.net |
whitehatsec.com.tw |
whitehatsec.org |
whitehatsec.me.uk |
whitehatsec.cc |
whitehatsec.tv |
Similar names
DNS History
11 records (6 active, 5 former)
●NSns17.domaincontrol.com2026-05-19 → 2026-07-30 · 3 obs
● 2026-05-19 20:49:54
● 2026-07-30 05:56:02
●NSns18.domaincontrol.com2026-05-19 → 2026-07-30 · 3 obs
● 2026-05-19 20:49:54
● 2026-07-30 05:56:02
○NSns51.domaincontrol.com2015-06-17 → 2020-01-08 · 4 obs
● 2020-01-08 21:36:08
○ 2026-05-19 20:49:54
○ 2026-07-30 05:56:02
○NSns52.domaincontrol.com2015-06-17 → 2020-01-08 · 4 obs
● 2020-01-08 21:36:08
○ 2026-05-19 20:49:54
○ 2026-07-30 05:56:02
●MXmailstore1.secureserver.net2015-06-17 → 2026-07-30 · 2 obs
● 2026-07-30 05:56:02
●MXsmtp.secureserver.net2015-06-17 → 2026-07-30 · 2 obs
● 2026-07-30 05:56:02
●A15.197.142.1732026-05-19 → 2026-07-30 · 3 obs
● 2026-05-19 20:49:54
● 2026-07-30 05:56:02
○A184.168.131.2412020-01-08 → 2020-01-08 · 4 obs
● 2020-01-08 21:36:08
○ 2026-05-19 20:49:54
○ 2026-07-30 05:56:02
●A3.33.152.1472026-05-19 → 2026-07-30 · 3 obs
● 2026-05-19 20:49:54
● 2026-07-30 05:56:02
○A50.63.202.302015-10-29 → 2017-02-16 · 5 obs
● 2015-10-29 14:13:08
● 2017-02-16 06:59:06
○ 2020-01-08 21:36:08
○ 2026-07-30 05:56:02
○A50.63.202.372015-06-17 → 2015-06-17 · 3 obs
○ 2015-10-29 14:13:08
○ 2026-07-30 05:56:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | h.gtld-servers.net, l.gtld-servers.net, i.gtld-servers.net, d.gtld-servers.net... | - |
| whitehatsec.net | ns17.domaincontrol.com, ns18.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.76.9
NS records: ns17.domaincontrol.com, ns18.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for whitehatsec.net (unsigned zone)
⏱️ Timing
Total: 378ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.142.173, 3.33.152.147 |
| NS | 2 | ns17.domaincontrol.com, ns18.domaincontrol.com |
| MX | 2 | smtp.secureserver.net (pri: 0), mailstore1.secureserver.net (pri: 10) |
| SOA | 1 | ns17.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
whitehatsec.net points to the IP addresses 3.33.152.147 and 15.197.142.173
Two other host names, along with mexicotravesias.com, emusicstore.com and suny.support, also share IP numbers with whitehatsec.net.
Name Servers
Two name servers handle the delegation for whitehatsec.net: ns17.domaincontrol.com and ns18.domaincontrol.com.
whitehatsec.net shares its NS records with other domains, for example avaisonco.com, foxintegratedhealthcare.com, factorfied.com and two others.
ns17.domaincontrol.com and ns18.domaincontrol.com both carry two IP addresses. The A records for ns17.domaincontrol.com are 97.74.108.9 and 2603:5:21c0::9; the A records for ns18.domaincontrol.com are 173.201.76.9 and 2603:5:22c0::9.
Mail Servers
whitehatsec.net is served by two mail servers, mailstore1.secureserver.net and smtp.secureserver.net.
Among the domains sharing a mail server setup with whitehatsec.net are laheartspecialists.com, careyperez.com, insidegen.com and two others.
whitehatsec.net and other domains — kansascityusergroups.com for instance — share at least some mail servers.
mailstore1.secureserver.net points to 216.69.141.78, 216.69.141.114 and 216.69.141.162. smtp.secureserver.net points to 216.69.141.71, 216.69.141.84 and 216.69.141.113. Both hosts resolve to three IP numbers.