headrequest.com - dns.ninja
headrequest.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns2.afternic.com ⭐ | ||||||
| A | 2603:5:2226::45🇺🇸 GODADDY-DNS2603:5:2220::/44 | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 173.201.66.69🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.afternic.com | ||||||
| NS | ns1.afternic.com | ||||||
| A | 2603:5:2126::45🇺🇸 GODADDY-DNS2603:5:2120::/44 | ||||||
| PTR | ns1.afternic.com | ||||||
| A | 97.74.98.69🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns1.afternic.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns2.afternic.comdns@jomax.net serial=1 | ||||||
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=1782723240 | ||||||
Same first word
headrequest.com |
DNS History
8 records (4 active, 4 former)
●NSns1.afternic.com2026-05-10 → 2026-06-29 · 3 obs
● 2026-05-10 15:52:08
● 2026-06-29 09:04:52
○NSns1.saltwaterdreams.com2017-01-02 → 2017-11-18 · 4 obs
● 2017-11-18 12:33:52
○ 2026-05-10 15:52:08
○ 2026-06-29 09:04:52
●NSns2.afternic.com2026-05-10 → 2026-06-29 · 3 obs
● 2026-05-10 15:52:08
● 2026-06-29 09:04:52
○MXmail.saltwaterdreams.com2017-01-02 → 2017-11-18 · 4 obs
● 2017-11-18 12:33:52
○ 2026-05-10 15:52:08
○ 2026-06-29 09:04:52
○A104.236.167.462017-11-18 → 2017-11-18 · 4 obs
● 2017-11-18 12:33:52
○ 2026-05-10 15:52:08
○ 2026-06-29 09:04:52
●A13.248.169.482026-05-10 → 2026-06-29 · 3 obs
● 2026-05-10 15:52:08
● 2026-06-29 09:04:52
○A70.32.78.2482017-01-02 → 2017-01-02 · 3 obs
○ 2017-11-18 12:33:52
○ 2026-06-29 09:04:52
●A76.223.54.1462026-05-10 → 2026-06-29 · 3 obs
● 2026-05-10 15:52:08
● 2026-06-29 09:04:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, l.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net... | - |
| headrequest.com | ns1.afternic.com, ns2.afternic.com | 4 records |
✅ Authoritative Response
Server:97.74.98.69
NS records: ns1.afternic.com, ns2.afternic.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for headrequest.com (unsigned zone)
⏱️ Timing
Total: 124ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 76.223.54.146, 13.248.169.48 |
| NS | 2 | ns1.afternic.com, ns2.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.afternic.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.afternic.com, ns1.afternic.com, ns2.afternic.com...)
Analysis
IP Addresses
headrequest.com has two IP addresses: 13.248.169.48 and 76.223.54.146
Additional host names — gondor.green-lemon.com, dyrw.com, tagpeer.com and two others — share IP numbers with headrequest.com.
Name Servers
DNS delegation for headrequest.com points to two name servers: ns1.afternic.com and ns2.afternic.com.
headrequest.com shares its name server setup with other domains, including myimports.com, xelesta.com, mx.symmetryconsulting.com and two others.
There is at least partial name server overlap between headrequest.com and other domains — chavo.us, kingmania.com, wwjdn.com and two more among them.
These name servers tend to appear in combination with the name servers verification-d3jclucsp89ganyqbydeny.ns101.verify.hn, verification-m3erh32ujyoastvophjvuz.ns101.verify.hn, verification-urj2ap2akmgcchkhharttb.ns101.verify.hn and verification-9ei4vxdecqgqfh6tmts4rw.ns101.verify.hn.
ns1.afternic.com directs to 97.74.98.69 and 2603:5:2126::45. ns2.afternic.com directs to 173.201.66.69 and 2603:5:2226::45. Each host name carries two IP addresses.