publicsectorcloud.com - robtex.com
publicsectorcloud.com
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=1771291435 | ||||||
Same first word
publicsectorcloud.com |
DNS History
11 records (8 active, 3 former)
●NSns1.markmonitor.com2026-02-18 → 2026-03-24 · 3 obs
● 2026-02-18 10:16:36
● 2026-03-24 11:02:36
○NSns1.namecity.com2015-08-17 → 2017-03-24 · 4 obs
● 2017-03-24 02:36:46
○ 2026-02-18 10:16:36
○ 2026-03-24 11:02:36
●NSns2.markmonitor.com2026-02-18 → 2026-03-24 · 3 obs
● 2026-02-18 10:16:36
● 2026-03-24 11:02:36
○NSns2.namecity.com2015-08-17 → 2017-03-24 · 4 obs
● 2017-03-24 02:36:46
○ 2026-02-18 10:16:36
○ 2026-03-24 11:02:36
●NSns3.markmonitor.com2026-02-18 → 2026-03-24 · 3 obs
● 2026-02-18 10:16:36
● 2026-03-24 11:02:36
●NSns4.markmonitor.com2026-02-18 → 2026-03-24 · 3 obs
● 2026-02-18 10:16:36
● 2026-03-24 11:02:36
●NSns5.markmonitor.com2026-02-18 → 2026-03-24 · 3 obs
● 2026-02-18 10:16:36
● 2026-03-24 11:02:36
●NSns6.markmonitor.com2026-02-18 → 2026-03-24 · 3 obs
● 2026-02-18 10:16:36
● 2026-03-24 11:02:36
●NSns7.markmonitor.com2026-02-18 → 2026-03-24 · 3 obs
● 2026-02-18 10:16:36
● 2026-03-24 11:02:36
●A3.33.139.322026-02-18 → 2026-03-24 · 3 obs
● 2026-02-18 10:16:36
● 2026-03-24 11:02:36
○A62.233.121.612015-08-17 → 2017-03-24 · 4 obs
● 2017-03-24 02:36:46
○ 2026-02-18 10:16:36
○ 2026-03-24 11:02:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, b.gtld-servers.net, d.gtld-servers.net, f.gtld-servers.net... | - |
| publicsectorcloud.com | ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com... | 12 records |
✅ Authoritative Response
Server:149.112.160.1
NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ns2.markmonitor.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for publicsectorcloud.com (unsigned zone)
⏱️ Timing
Total: 745ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 3.33.139.32 |
| NS | 7 | ns1.markmonitor.com, ns2.markmonitor.com... |
| SOA | 1 | ns1.markmonitor.com hostmaster.markmonit |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (ns1.markmonitor.com, ns1.markmonitor.com, ns3.markmonitor.com...)
Analysis
IP Addresses
publicsectorcloud.com resolves to a single IP: 3.33.139.32.
Other host names, for instance wkudining.com, aarpglobalnetwork.org, www.ebayannunci.it, dealerextranet.westinghousehvac.com and fico9.mobi share IP numbers with publicsectorcloud.com.
Name Servers
publicsectorcloud.com is delegated to seven name servers: ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.
publicsectorcloud.com shares some name servers with other domains, for example telegraphshop.uk, thecentre.eu, axa-express.de, looble.us and shutterstockllc.com.
Host names with two IP numbers:
ns1.markmonitor.com points to: 2620:10a:80a8::1 and 149.112.160.1; ns2.markmonitor.com points to: 2001:67c:10b8::1 and 176.97.158.1; ns3.markmonitor.com points to: 2620:10a:80a9::1 and 149.112.161.1; ns4.markmonitor.com points to: 2001:67c:1bc::1 and 192.174.68.1; ns5.markmonitor.com points to: 2620:10a:80a8::2 and 149.112.160.2; ns6.markmonitor.com points to: 2001:67c:10b8::3 and 176.97.158.3; ns7.markmonitor.com points to: 2620:10a:80a9::2 and 149.112.161.2.