32036.com - robtex.com
32036.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 | ns5.afternic.com ⭐ | ||||||
| A | 2603:5:2134::42🇺🇸 GODADDY-DNS2603:5:2130::/44 | ||||||
| PTR | ns5.afternic.com | ||||||
| A | 97.74.99.66🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns5.afternic.com | ||||||
| NS | ns6.afternic.com | ||||||
| A | 2603:5:2234::42🇺🇸 GODADDY-DNS2603:5:2230::/44 | ||||||
| PTR | ns6.afternic.com | ||||||
| A | 173.201.67.66🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns6.afternic.com | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns5.afternic.comdns@jomax.net 2025-09-30 #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=1784279107 | ||||||
Same first word
Similar names
DNS History
12 records (4 active, 8 former)
●NSns5.afternic.com2026-07-04 → 2026-07-17 · 3 obs
● 2026-07-04 15:26:38
● 2026-07-17 09:24:08
●NSns6.afternic.com2026-07-04 → 2026-07-17 · 3 obs
● 2026-07-04 15:26:38
● 2026-07-17 09:24:08
○NSwww.32036.com2015-06-20 → 2017-02-09 · 4 obs
● 2017-02-09 03:26:26
○ 2026-07-04 15:26:38
○ 2026-07-17 09:24:08
○MXio.bouncemx.com2015-11-16 → 2017-02-09 · 4 obs
● 2017-02-09 03:26:26
○ 2026-07-04 15:26:38
○ 2026-07-17 09:24:08
○A104.160.171.792017-02-09 → 2017-02-09 · 4 obs
● 2017-02-09 03:26:26
○ 2018-08-22 16:44:08
○ 2026-07-17 09:24:08
○A124.16.31.1432015-06-20 → 2016-04-24 · 4 obs
● 2016-04-24 18:36:12
○ 2017-02-09 03:26:26
○ 2026-07-17 09:24:08
●A13.248.169.482026-07-04 → 2026-07-17 · 3 obs
● 2026-07-04 15:26:38
● 2026-07-17 09:24:08
●A76.223.54.1462026-07-04 → 2026-07-17 · 3 obs
● 2026-07-04 15:26:38
● 2026-07-17 09:24:08
○CNAME5.do94.cn2015-06-20 → 2015-06-20 · 3 obs
○ 2015-11-16 00:36:34
○ 2026-07-17 09:24:08
○CNAMEb371wyj.yb550.com2018-08-22 → 2018-08-22 · 4 obs
● 2018-08-22 16:44:08
○ 2026-07-04 15:26:38
○ 2026-07-17 09:24:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| 32036.com | ns5.afternic.com, ns6.afternic.com | 2 records |
✅ Authoritative Response
Server:97.74.99.66
NS records: ns5.afternic.com, ns6.afternic.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 32036.com (unsigned zone)
⏱️ Timing
Total: 120ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 13.248.169.48, 76.223.54.146 |
| NS | 2 | ns5.afternic.com, ns6.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns5.afternic.com dns.jomax.net |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns5.afternic.com, ns6.afternic.com)
Analysis
IP Addresses
32036.com has two IP addresses: 13.248.169.48 and 76.223.54.146
wp-includes.blog.rsp18.com, nurmobile.com, parasut.net plus two other host names have IP numbers in common with 32036.com.
Name Servers
The NS records for 32036.com delegate to ns5.afternic.com and ns6.afternic.com.
The name server configuration of 32036.com is shared with other domains, for instance uey.us, am777.cc, www.deepcum.com and two others.
The name servers of 32036.com overlap at least partially with those of other domains — among them serchief.xyz, hempcity.xyz, hedgeliquidstake.xyz and two more.
These name servers commonly appear alongside the name servers verification-gakbzzzqmt6gkcplw4efpp.ns101.verify.hn and verification-qpk69stxhfddweejynqfmn.ns101.verify.hn.
ns5.afternic.com resolves to 97.74.99.66 and 2603:5:2134::42. Likewise, ns6.afternic.com resolves to 173.201.67.66 and 2603:5:2234::42 — two IP addresses apiece.