hetbot.com - dns.ninja
hetbot.com
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=1783848537 | ||||||
Same first word
hetbot.com |
Similar names
DNS History
11 records (9 active, 2 former)
●MXalt1.aspmx.l.google.com2026-04-01 → 2026-07-12 · 3 obs
● 2026-04-01 17:52:02
● 2026-07-12 09:58:02
●MXalt2.aspmx.l.google.com2026-04-01 → 2026-07-12 · 3 obs
● 2026-04-01 17:52:02
● 2026-07-12 09:58:02
●MXalt3.aspmx.l.google.com2026-04-01 → 2026-07-12 · 3 obs
● 2026-04-01 17:52:02
● 2026-07-12 09:58:02
●MXalt4.aspmx.l.google.com2026-04-01 → 2026-07-12 · 3 obs
● 2026-04-01 17:52:02
● 2026-07-12 09:58:02
●MXaspmx.l.google.com2026-04-01 → 2026-07-12 · 3 obs
● 2026-04-01 17:52:02
● 2026-07-12 09:58:02
○MXredirect.ovh.net2020-02-05 → 2020-02-05 · 3 obs
○ 2026-04-01 17:52:02
○ 2026-07-12 09:58:02
●A2001:41d0:301:5::312026-04-01 → 2026-07-12 · 3 obs
● 2026-04-01 17:52:02
● 2026-07-12 09:58:02
●A87.98.236.2532026-04-01 → 2026-07-12 · 3 obs
● 2026-04-01 17:52:02
● 2026-07-12 09:58:02
○A87.98.239.52020-02-05 → 2020-02-05 · 3 obs
○ 2026-04-01 17:52:02
○ 2026-07-12 09:58:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, d.gtld-servers.net, m.gtld-servers.net, b.gtld-servers.net... | - |
| hetbot.com | dns103.ovh.net, ns103.ovh.net | - |
✅ Authoritative Response
Server:5.196.39.89
NS records: dns103.ovh.net, ns103.ovh.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for hetbot.com (unsigned zone)
⏱️ Timing
Total: 974ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 87.98.236.253 |
| AAAA | 1 | 2001:41d0:301:5::31 |
| NS | 2 | dns103.ovh.net, ns103.ovh.net |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), aspmx.l.google.com (pri: 1)... |
| TXT | 5 | google-site-verification=LQIN6BPuWINwV_L, google-site-verification=e9Z-xBPzY61cqct... |
| SOA | 1 | dns103.ovh.net tech.ovh.net |
Analysis
IP Addresses
hetbot.com points to the IP addresses 87.98.236.253 and 2001:41d0:301:5::31
Additional host names — jindos.net, inguri.eu, shotsudrift.com and two others — share IP numbers with hetbot.com.
Name Servers
DNS delegation for hetbot.com points to two name servers: dns103.ovh.net and ns103.ovh.net.
hetbot.com shares its name server setup with other domains, including gorazar.pl, sooshi.it, mathieuheliot.com and two others.
dns103.ovh.net directs to 5.196.39.89 and 2001:41d0:d00:fd00::2. ns103.ovh.net directs to 5.135.54.65 and 2001:41d0:b00:f700::2. Each host name carries two IP addresses.
Mail Servers
hetbot.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
hetbot.com shares mail servers — at least in part — with other domains, including wolf-pac.com, sdpi.jp, johnwest.consulting and two others.
These mail servers are frequently used alongside mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other.
Host names with two IP numbers:
aspmx.l.google.com has two IP addresses: 142.251.16.26 and 2607:f8b0:4004:c17::1b.
alt1.aspmx.l.google.com has two IP addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com has two IP addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com has two IP addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com has two IP addresses: 172.253.157.26 and 2a00:1450:400c:c23::1b.