leadanizer.dev - dns.ninja
leadanizer.dev
| DNSSEC | ⚠️ Not signed | ||||||
| A | 165.245.215.206🇺🇸 UNSPECIFIED160.0.0.0/3 | ||||||
| NS | ns1.digitalocean.com ⭐ | ||||||
| A | 2606:4700:52::ac40:34d2🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| A | 172.64.52.210🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.digitalocean.com | ||||||
| NS | ns2.digitalocean.com | ||||||
| A | 2606:4700:5a::ac40:3515🇺🇸 Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| A | 172.64.53.21🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.digitalocean.com | ||||||
| NS | ns3.digitalocean.com | ||||||
| A | 2606:4700:52::ac40:31d1🇺🇸 Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| A | 172.64.49.209🇺🇸 Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns3.digitalocean.com | ||||||
| NS | ns4.digitalocean.com ⚠️ Not in zone NS records | ||||||
| SOA | ns1.digitalocean.comhostmaster@leadanizer.dev serial=0 | ||||||
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
Similar names
Previous names
Next names
DNS History
5 records (5 active, 0 former)
●NSns1.digitalocean.com2026-09-19 → 2026-10-01 · 2 obs
● 2026-10-01 06:31:16
●NSns2.digitalocean.com2026-09-19 → 2026-10-01 · 2 obs
● 2026-10-01 06:31:16
●NSns3.digitalocean.com2026-09-19 → 2026-10-01 · 2 obs
● 2026-10-01 06:31:16
●NSns4.digitalocean.com2026-09-19 → 2026-10-01 · 2 obs
● 2026-10-01 06:31:16
●A165.245.215.2062026-09-19 → 2026-10-01 · 2 obs
● 2026-10-01 06:31:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | - |
| leadanizer.dev | ns2.digitalocean.com, ns4.digitalocean.com, ns3.digitalocean.com, ns1.digitalocean.com | - |
✅ Authoritative Response
Server:172.64.52.210
NS records: ns2.digitalocean.com, ns4.digitalocean.com, ns3.digitalocean.com, ns1.digitalocean.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leadanizer.dev (unsigned zone)
⏱️ Timing
Total: 711ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 165.245.215.206 |
| NS | 3 | ns1.digitalocean.com, ns3.digitalocean.com... |
| SOA | 1 | ns1.digitalocean.com hostmaster.leadaniz |
Analysis
IP Addresses
leadanizer.dev has exactly one IP address — 165.245.215.206.
Name Servers
Four name servers handle the delegation for leadanizer.dev: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com and ns4.digitalocean.com.
leadanizer.dev shares at least some of its name servers with other domains, including boatfacts.app, servicio-tecnico-balay-marbella.es, warwicksremovals.co.uk and two others.
The hostnames ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com each direct to two IP addresses — ns1.digitalocean.com to 172.64.52.210 and 2606:4700:52::ac40:34d2, ns2.digitalocean.com to 172.64.53.21 and 2606:4700:5a::ac40:3515, and ns3.digitalocean.com to 172.64.49.209 and 2606:4700:52::ac40:31d1.