halandy.com - dns.ninja
halandy.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=1786383049 | ||||||
Same first word
halandy.com |
Similar names
DNS History
9 records (9 active, 0 former)
●NSns57.domaincontrol.com2026-03-25 → 2026-08-10 · 2 obs
● 2026-08-10 17:59:52
●NSns58.domaincontrol.com2026-03-25 → 2026-08-10 · 2 obs
● 2026-08-10 17:59:52
●MXalt1.aspmx.l.google.com2026-03-25 → 2026-08-10 · 2 obs
● 2026-08-10 17:59:52
●MXalt2.aspmx.l.google.com2026-03-25 → 2026-08-10 · 2 obs
● 2026-08-10 17:59:52
●MXalt3.aspmx.l.google.com2026-03-25 → 2026-08-10 · 2 obs
● 2026-08-10 17:59:52
●MXalt4.aspmx.l.google.com2026-03-25 → 2026-08-10 · 2 obs
● 2026-08-10 17:59:52
●MXaspmx.l.google.com2026-03-25 → 2026-08-10 · 2 obs
● 2026-08-10 17:59:52
●A15.197.148.332026-03-25 → 2026-08-10 · 2 obs
● 2026-08-10 17:59:52
●A3.33.130.1902026-03-25 → 2026-08-10 · 2 obs
● 2026-08-10 17:59:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| halandy.com | ns57.domaincontrol.com, ns58.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.76.29
NS records: ns57.domaincontrol.com, ns58.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for halandy.com (unsigned zone)
⏱️ Timing
Total: 138ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns57.domaincontrol.com, ns58.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 include:dc-aa8e722993._spfm.halan, google-site-verification=ZaIgkBkMmaVedhz |
| SOA | 1 | ns57.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns57.domaincontrol.com, ns57.domaincontrol.com, ns58.domaincontrol.com...)
Analysis
IP Addresses
halandy.com resolves to the IP addresses 3.33.130.190 and 15.197.148.33
Two other host names, along with ontheamericantrail.com, refipoint.com and skymyo.com, also share IP numbers with halandy.com.
Name Servers
halandy.com uses two name servers for its delegation: ns57.domaincontrol.com and ns58.domaincontrol.com.
halandy.com shares its NS records with other domains, for example clockpoint.net, paulmassaro.net, indianamortgagecompany.net and two others.
The two host names ns57.domaincontrol.com and ns58.domaincontrol.com each have a pair of IP addresses: ns57.domaincontrol.com has 97.74.108.29 and 2603:5:21c2::1d, and ns58.domaincontrol.com has 173.201.76.29 and 2603:5:22c2::1d.
Mail Servers
halandy.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between halandy.com and other domains, including ns500693.ns500693.ns500734.ns500693.ns500693.ns500699.ns500734.ns500699.ns500699.ns500693.ns500693.ns500632.ns500588.ns500612.ns500588.ns500588.dtrkdll.com, uj-fashion.in, pbagalleries.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com directs traffic to 172.253.122.27 and 2607:f8b0:4004:c21::1b.
alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.