towerborn.com - dns.ninja
towerborn.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 20.70.246.20🇦🇺 Microsoft20.64.0.0/10 | ||||||
| A | 20.76.201.171🇳🇱 Microsoft20.64.0.0/10 | ||||||
| A | 20.112.250.133🇺🇸 Microsoft20.64.0.0/10 | ||||||
| A | 20.231.239.246🇺🇸 Microsoft20.192.0.0/10 | ||||||
| A | 20.236.44.162🇺🇸 Microsoft20.192.0.0/10 | ||||||
| NS | ns1-36.azure-dns.com ⭐ | ||||||
| A | 2603:1061:0:10::24🇺🇸 Microsoft2603:1000::/25 MICROSOFT | ||||||
| PTR | ns1-36.azure-dns.com | ||||||
| A | 150.171.10.36🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns1-36.azure-dns.com | ||||||
| NS | ns2-36.azure-dns.net | ||||||
| A | 2620:1ec:8ec:10::24🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns2-36.azure-dns.net | ||||||
| A | 150.171.16.36🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-36.azure-dns.net | ||||||
| NS | ns3-36.azure-dns.org | ||||||
| A | 2a01:111:4000:10::24🇬🇧 Microsoft2a01:111:4000::/36 | ||||||
| PTR | ns3-36.azure-dns.org | ||||||
| A | 13.107.222.36🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns3-36.azure-dns.org | ||||||
| NS | ns4-36.azure-dns.info | ||||||
| A | 2620:1ec:bda:10::24🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns4-36.azure-dns.info | ||||||
| A | 13.107.206.36🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns4-36.azure-dns.info | ||||||
| SOA | ns1-36.azure-dns.comazuredns-hostmaster@microsoft.com serial=1 | ||||||
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=1782619975 | ||||||
Same first word
towerborn.com |
Similar names
DNS History
9 records (9 active, 0 former)
●NSns1-36.azure-dns.com2026-02-28 → 2026-06-28 · 2 obs
● 2026-06-28 04:23:08
●NSns2-36.azure-dns.net2026-02-28 → 2026-06-28 · 2 obs
● 2026-06-28 04:23:08
●NSns3-36.azure-dns.org2026-02-28 → 2026-06-28 · 2 obs
● 2026-06-28 04:23:08
●NSns4-36.azure-dns.info2026-02-28 → 2026-06-28 · 2 obs
● 2026-06-28 04:23:08
●A20.112.250.1332026-02-28 → 2026-06-28 · 2 obs
● 2026-06-28 04:23:08
●A20.231.239.2462026-02-28 → 2026-06-28 · 2 obs
● 2026-06-28 04:23:08
●A20.236.44.1622026-02-28 → 2026-06-28 · 2 obs
● 2026-06-28 04:23:08
●A20.70.246.202026-02-28 → 2026-06-28 · 2 obs
● 2026-06-28 04:23:08
●A20.76.201.1712026-02-28 → 2026-06-28 · 2 obs
● 2026-06-28 04:23:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| towerborn.com | ns1-36.azure-dns.com, ns2-36.azure-dns.net, ns4-36.azure-dns.info, ns3-36.azure-dns.org | 2 records |
✅ Authoritative Response
Server:150.171.10.36
NS records: ns1-36.azure-dns.com, ns2-36.azure-dns.net, ns4-36.azure-dns.info, ns3-36.azure-dns.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for towerborn.com (unsigned zone)
⏱️ Timing
Total: 298ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 5 | 20.76.201.171, 20.236.44.162... |
| NS | 4 | ns1-36.azure-dns.com, ns2-36.azure-dns.net... |
| SOA | 1 | ns1-36.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-36.azure-dns.com, ns1-36.azure-dns.com)
Analysis
IP Addresses
towerborn.com directs to five IP numbers, including 20.70.246.20, 20.76.201.171, 20.112.250.133 and two others
2018xbox.com, hotmailpayments.net, buy-hotmail.us plus two other host names have IP numbers in common with towerborn.com.
Name Servers
Four name servers handle the delegation for towerborn.com: ns1-36.azure-dns.com, ns4-36.azure-dns.info, ns2-36.azure-dns.net and ns3-36.azure-dns.org.
There is at least partial name server overlap between towerborn.com and other domains — wendyswantstoknow.com, ingramfinancialgroup.net, crowngreensboro.com and two more among them.
All four hostnames — ns1-36.azure-dns.com, ns4-36.azure-dns.info, ns2-36.azure-dns.net and ns3-36.azure-dns.org — resolve to two IP numbers apiece: ns1-36.azure-dns.com to 150.171.10.36 and 2603:1061:0:10::24; ns4-36.azure-dns.info to 13.107.206.36 and 2620:1ec:bda:10::24; ns2-36.azure-dns.net to 150.171.16.36 and 2620:1ec:8ec:10::24; ns3-36.azure-dns.org to 13.107.222.36 and 2a01:111:4000:10::24.