publicsector.us - robtex.com
publicsector.us
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1-08.azure-dns.com ⭐ | ||||||
| A | 2603:1061:0:700::8🇺🇸 Microsoft2603:1000::/25 MICROSOFT | ||||||
| PTR | ns1-08.azure-dns.com | ||||||
| A | 13.107.236.8🇺🇸 Microsoft13.104.0.0/14 MICROSOFT | ||||||
| PTR | ns1-08.azure-dns.com | ||||||
| NS | ns2-08.azure-dns.net | ||||||
| A | 2620:1ec:8ec:700::8🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns2-08.azure-dns.net | ||||||
| A | 150.171.21.8🇺🇸 Microsoft150.171.0.0/16 MICROSOFT | ||||||
| PTR | ns2-08.azure-dns.net | ||||||
| NS | ns3-08.azure-dns.org | ||||||
| A | 2a01:111:4000:700::8🇬🇧 Microsoft2a01:111:4000::/36 | ||||||
| PTR | ns3-08.azure-dns.org | ||||||
| A | 204.14.183.8🇺🇸 Microsoft204.14.180.0/22 | ||||||
| PTR | ns3-08.azure-dns.org | ||||||
| NS | ns4-08.azure-dns.info | ||||||
| A | 2620:1ec:bda:700::8🇺🇸 Microsoft2620:1ec::/36 MICROSOFT | ||||||
| PTR | ns4-08.azure-dns.info | ||||||
| A | 208.84.5.8🇺🇸 Microsoft208.84.0.0/21 MICROSOFT | ||||||
| PTR | ns4-08.azure-dns.info | ||||||
| SOA | ns1-08.azure-dns.comazuredns-hostmaster@microsoft.com serial=1 | ||||||
us
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.cctld.us ⭐ | ||||||
| NS | b.cctld.us | ||||||
| NS | f.cctld.us | ||||||
| NS | k.cctld.us | ||||||
| NS | m.cctld.us | ||||||
| NS | n.cctld.us | ||||||
| NS | w.cctld.us | ||||||
| NS | x.cctld.us | ||||||
| NS | y.cctld.us | ||||||
| SOA | a.cctld.usadmin@tldns.godaddy serial=1774566977 | ||||||
Same first word
publicsector.digital |
publicsector.sa.gov.au |
publicsector.com.au |
publicsector.it |
publicsector.wa.gov.au |
publicsector.de |
publicsector.google |
publicsector.nl |
publicsector.ca |
publicsector.us |
Similar names
DNS History
4 records (4 active, 0 former)
●NSns1-08.azure-dns.com2026-02-28 → 2026-03-26 · 2 obs
● 2026-03-26 23:34:48
●NSns2-08.azure-dns.net2026-02-28 → 2026-03-26 · 2 obs
● 2026-03-26 23:34:48
●NSns3-08.azure-dns.org2026-02-28 → 2026-03-26 · 2 obs
● 2026-03-26 23:34:48
●NSns4-08.azure-dns.info2026-02-28 → 2026-03-26 · 2 obs
● 2026-03-26 23:34:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| us | m.cctld.us, k.cctld.us, b.cctld.us, x.cctld.us... | - |
| publicsector.us | ns4-08.azure-dns.info, ns3-08.azure-dns.org, ns1-08.azure-dns.com, ns2-08.azure-dns.net | - |
✅ Authoritative Response
Server:208.84.5.8
NS records: ns4-08.azure-dns.info, ns3-08.azure-dns.org, ns1-08.azure-dns.com, ns2-08.azure-dns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for publicsector.us (unsigned zone)
⏱️ Timing
Total: 1268ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1-08.azure-dns.com, ns2-08.azure-dns.net... |
| SOA | 1 | ns1-08.azure-dns.com azuredns-hostmaster |
Analysis
Name Servers
publicsector.us is delegated to four name servers: ns1-08.azure-dns.com, ns4-08.azure-dns.info, ns2-08.azure-dns.net and ns3-08.azure-dns.org.
publicsector.us at least partially shares name servers with other domains such as smandy.net, usgovcloudapi.com, wwwmicrosoftcom.org, 2.130.0.95.in-addr.arpa and thamesluxurycharters.co.uk.
Host names with two IP numbers:
ns1-08.azure-dns.com points to 2603:1061:0:700::8 and 13.107.236.8
ns4-08.azure-dns.info points to 2620:1ec:bda:700::8 and 208.84.5.8
ns2-08.azure-dns.net points to 2620:1ec:8ec:700::8 and 150.171.21.8
ns3-08.azure-dns.org points to 2a01:111:4000:700::8 and 204.14.183.8