blaze.to checked at 2025-02-11T14:00:54.274Z 178ms 62/62/62 100% R:9
DNS.NINJA - blaze.to
Search for IP or hostnames
blaze.to
NS | ns1.digitalocean.com | ||||||
A | 2606:4700:52::ac40:34d2 🇺🇸 Cloudflare | ||||||
PTR | ns1.digitalocean.com | ||||||
A | 172.64.52.210🇺🇸 Cloudflare | ||||||
PTR | ns1.digitalocean.com | ||||||
NS | ns2.digitalocean.com | ||||||
A | 2606:4700:5a::ac40:3515 🇺🇸 Cloudflare | ||||||
PTR | ns2.digitalocean.com | ||||||
A | 172.64.53.21🇺🇸 Cloudflare | ||||||
PTR | ns2.digitalocean.com | ||||||
NS | ns3.digitalocean.com | ||||||
A | 2606:4700:52::ac40:31d1 🇺🇸 Cloudflare | ||||||
PTR | ns3.digitalocean.com | ||||||
A | 172.64.49.209🇺🇸 Cloudflare | ||||||
PTR | ns3.digitalocean.com | ||||||
A | 159.203.255.68🇺🇸 DigitalOcean |
to
NS | tonic.to | ||||||
NS | cd5.tonic.to | ||||||
NS | cd6.tonic.to | ||||||
NS | cd7.tonic.to | ||||||
NS | cd8.tonic.to | ||||||
NS | frankfurt.tonic.to | ||||||
NS | helsinki.tonic.to | ||||||
NS | la.tonic.to | ||||||
NS | newyork.tonic.to | ||||||
NS | singapore.tonic.to | ||||||
NS | sydney.tonic.to |
AI analysis
159.203.255.68 is the IP address that blaze.to points to.
Three name servers, ns1.digitalocean.com, ns2.digitalocean.com, and ns3.digitalocean.com, have been delegated to blaze.to.
The name server setup for blaze.to is shared with other domains such as 117.199.24.in-addr.arpa, arutha.lk, gosznak-diploms.com, discoverion.com, and schetitoti.com.
The domain blaze.to shares at least a portion of its name servers with other domains such as royalauto.in and vexatos.com.
ns1.digitalocean.com, 2606:4700:52::ac40:34d2, and 172.64.52.210 are associated together.
ns2.digitalocean.com, 2606:4700:5a::ac40:3515, and 172.64.53.21 are connected.
ns3.digitalocean.com, 2606:4700:52::ac40:31d1, and 172.64.49.209 are linked.
dbq