hackam.com - dns.ninja
hackam.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=1781274398 | ||||||
Same first word
hackam.com |
Similar names
DNS History
13 records (13 active, 0 former)
●NSns11.domaincontrol.com2015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●NSns12.domaincontrol.com2015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●MXalt1.aspmx.l.google.com2015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●MXalt2.aspmx.l.google.com2015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●MXaspmx.l.google.com2015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●MXaspmx2.googlemail.com2015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●MXaspmx3.googlemail.com2015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●MXaspmx4.googlemail.com2015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●MXaspmx5.googlemail.com2015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●A216.239.32.212015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●A216.239.34.212015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●A216.239.36.212015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
●A216.239.38.212015-08-04 → 2026-06-12 · 2 obs
● 2026-06-12 14:45:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net... | - |
| hackam.com | ns11.domaincontrol.com, ns12.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.105.6
NS records: ns11.domaincontrol.com, ns12.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for hackam.com (unsigned zone)
⏱️ Timing
Total: 405ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 216.239.32.21, 216.239.34.21... |
| NS | 2 | ns11.domaincontrol.com, ns12.domaincontrol.com |
| MX | 7 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 20)... |
| SOA | 1 | ns11.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns11.domaincontrol.com, ns11.domaincontrol.com, ns12.domaincontrol.com...)
Analysis
IP Addresses
hackam.com points to four IP numbers: 216.239.32.21, 216.239.34.21, 216.239.36.21 and 216.239.38.21.
raccy.org, solential.com, oklae.com plus two other host names have IP numbers in common with hackam.com.
Name Servers
hackam.com uses two name servers for its delegation: ns11.domaincontrol.com and ns12.domaincontrol.com.
The name server configuration of hackam.com is shared with other domains, for instance snapsports.in, realseguroviaje.com, safety-kleen.de and two others.
At least some of hackam.com's name servers are also used by other domains, among them sonax.co.il.
The two host names ns11.domaincontrol.com and ns12.domaincontrol.com each have a pair of IP addresses: ns11.domaincontrol.com has 97.74.105.6 and 2603:5:2190::6, and ns12.domaincontrol.com has 173.201.73.6 and 2603:5:2290::6.
Mail Servers
hackam.com is handled by 7 mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.
At least some of the mail servers used by hackam.com are shared with other domains: kryojen.com, ns500699.ns500734.ns500734.ns500728.ns500588.ns500632.ns500632.ns500588.ns500588.ns500588.ns500588.dtrkdll.com, ns500759.ns500759.ns500759.ns500736.ns500698.ns500735.ns500735.ns500736.ns500698.ns500576.ns500698.ns500686.ns500619.ns500619.ns500576.trackreceptor.com and two others among them.
These mail servers are often deployed together with alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com directs traffic to 142.250.102.27 and 2a00:1450:4025:402::1a.
aspmx3.googlemail.com directs traffic to 192.178.213.26 and 2a00:1450:4013:c1e::1a.
aspmx4.googlemail.com directs traffic to 172.253.135.27 and 2607:f8b0:4023:1015::1a.
aspmx5.googlemail.com directs traffic to 142.250.147.27 and 2a00:1450:4025:c01::1b.
aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt1.aspmx.l.google.com directs traffic to 142.250.102.27 and 2a00:1450:4025:402::1a.
alt2.aspmx.l.google.com directs traffic to 192.178.213.26 and 2a00:1450:4013:c1e::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2a00:1450:4025:402::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 142.250.102.27 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 192.178.213.26 IP addresses each.