destroy.tokyo - robtex.com

destroy.tokyo

DNSSEC⚠️ Not signed
NSns1.digitalocean.com ⭐
A2606:4700:52::ac40:34d2πŸ‡ΊπŸ‡Έ Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns1.digitalocean.com
A172.64.52.210πŸ‡ΊπŸ‡Έ Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns1.digitalocean.com
NSns2.digitalocean.com
A2606:4700:5a::ac40:3515πŸ‡ΊπŸ‡Έ Cloudflare2606:4700:5a::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns2.digitalocean.com
A172.64.53.21πŸ‡ΊπŸ‡Έ Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns2.digitalocean.com
NSns3.digitalocean.com
A2606:4700:52::ac40:31d1πŸ‡ΊπŸ‡Έ Cloudflare2606:4700:52::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns3.digitalocean.com
A172.64.49.209πŸ‡ΊπŸ‡Έ Cloudflare172.64.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns3.digitalocean.com
TXTv=spf1 -all
SOAns1.digitalocean.comhostmaster@destroy.tokyo serial=1774404500

tokyo

DNSSECπŸ”’ Signed (DS record present)
NSa.gmoregistry.net ⭐
NSb.gmoregistry.net
NSk.gmoregistry.net
NSl.gmoregistry.net
SOAa.gmoregistry.netnoc@gmoregistry.net serial=1776067356

Subdomains

Same first word

Similar names

DNS History

3 records (3 active, 0 former)

NSns1.digitalocean.comns2.digitalocean.comns3.digitalocean.com
●NSns1.digitalocean.com2026-03-30 β†’ 2026-04-13 Β· 2 obs
● 2026-03-30 01:19:28
● 2026-04-13 08:42:56
●NSns2.digitalocean.com2026-03-30 β†’ 2026-04-13 Β· 2 obs
● 2026-03-30 01:19:28
● 2026-04-13 08:42:56
●NSns3.digitalocean.com2026-03-30 β†’ 2026-04-13 Β· 2 obs
● 2026-03-30 01:19:28
● 2026-04-13 08:42:56

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
tokyoa.gmoregistry.net, l.gmoregistry.net, k.gmoregistry.net, b.gmoregistry.net7 records
destroy.tokyons2.digitalocean.com, ns3.digitalocean.com, ns1.digitalocean.com-

βœ… Authoritative Response

Server:172.64.53.21

NS records: ns2.digitalocean.com, ns3.digitalocean.com, ns1.digitalocean.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for destroy.tokyo (unsigned zone)

⏱️ Timing

Total: 259ms | Queries: -

πŸ“„ Records

TypeCountSample Data
NS3ns3.digitalocean.com, ns1.digitalocean.com...
TXT1v=spf1 -all
SOA1ns1.digitalocean.com hostmaster.destroy.

πŸ“Œ Glue Records Collected

Total: 7

Out-of-bailiwick: 7 (l.gmoregistry.net, k.gmoregistry.net, b.gmoregistry.net...)

Analysis

Hierarchy

i.destroy.tokyo has destroy.tokyo as its parent.

Name Servers

destroy.tokyo is delegated to name servers ns1.digitalocean.com, ns2.digitalocean.com and ns3.digitalocean.com.

destroy.tokyo at least partially shares name servers with other domains such as dragonflycentre.ca, brentjimenez.com, wizzlove.com, parseanalytics.com and enmongroup.com.

Host names with two IP numbers:

ns1.digitalocean.com points to 2606:4700:52::ac40:34d2 and 172.64.52.210.

ns2.digitalocean.com points to 2606:4700:5a::ac40:3515 and 172.64.53.21.

ns3.digitalocean.com points to 2606:4700:52::ac40:31d1 and 172.64.49.209.