trydispatch.app - dns.ninja
trydispatch.app
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1-35.azure-dns.com ⚠️ Not in zone NS records | ||||||
| A | 2603:1061:0:10::23🇺🇸 Microsoft2603:1000::/25 MICROSOFT | ||||||
| PTR | ns1-35.azure-dns.com | ||||||
| A | 150.171.10.35🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns1-35.azure-dns.com | ||||||
| NS | ns2-35.azure-dns.net ⚠️ Not in zone NS records | ||||||
| A | 2620:1ec:8ec:10::23🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns2-35.azure-dns.net | ||||||
| A | 150.171.16.35🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-35.azure-dns.net | ||||||
| NS | ns3-35.azure-dns.org ⚠️ Not in zone NS records | ||||||
| A | 2a01:111:4000:10::23🇬🇧 Microsoft2a01:111:4000::/36 | ||||||
| PTR | ns3-35.azure-dns.org | ||||||
| A | 13.107.222.35🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns3-35.azure-dns.org | ||||||
| NS | ns4-35.azure-dns.info ⚠️ Not in zone NS records | ||||||
| A | 2620:1ec:bda:10::23🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns4-35.azure-dns.info | ||||||
| A | 13.107.206.35🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns4-35.azure-dns.info | ||||||
app
| 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=101427 | ||||||
Same first word
trydispatch.com |
trydispatch.net |
trydispatch.io |
trydispatch.app |
trydispatch.co |
trydispatch.cc |
trydispatch.us |
trydispatch.com.ph |
trydispatch.ai |
trydispatch.xyz |
Similar names
Previous names
Next names
DNS History
4 records (4 active, 0 former)
●NSns1-35.azure-dns.com2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 15:06:18
●NSns2-35.azure-dns.net2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 15:06:18
●NSns3-35.azure-dns.org2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 15:06:18
●NSns4-35.azure-dns.info2026-09-08 → 2026-09-27 · 2 obs
● 2026-09-27 15:06:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| app | ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com... | 10 records |
| trydispatch.app | ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org, ns4-35.azure-dns.info | - |
✅ Authoritative Response
Server:150.171.10.35
NS records: ns1-35.azure-dns.com, ns2-35.azure-dns.net, ns3-35.azure-dns.org, ns4-35.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for trydispatch.app (unsigned zone)
⏱️ Timing
Total: 574ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
Name Servers
The NS records for trydispatch.app point to four name servers: ns1-35.azure-dns.com, ns4-35.azure-dns.info, ns2-35.azure-dns.net and ns3-35.azure-dns.org.
There is at least partial name server overlap between trydispatch.app and other domains — b4si.co.uk, qrpalaute.fi, avans.nl and two more among them.
All four hostnames — ns1-35.azure-dns.com, ns4-35.azure-dns.info, ns2-35.azure-dns.net and ns3-35.azure-dns.org — resolve to two IP numbers apiece: ns1-35.azure-dns.com to 150.171.10.35 and 2603:1061:0:10::23; ns4-35.azure-dns.info to 13.107.206.35 and 2620:1ec:bda:10::23; ns2-35.azure-dns.net to 150.171.16.35 and 2620:1ec:8ec:10::23; ns3-35.azure-dns.org to 13.107.222.35 and 2a01:111:4000:10::23.