adp.community - robtex.com
adp.community
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ha1.markmonitor.zone ⭐ | ||||||
| A | 2001:67c:1bc::5🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast | ||||||
| PTR | ha1.markmonitor.zone | ||||||
| A | 192.174.68.5🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net | ||||||
| PTR | ha1.markmonitor.zone | ||||||
| NS | ha2.markmonitor.zone | ||||||
| A | 2620:10a:80eb::6b🇨🇦 CIRA-22620:10a:80eb::/48 D-Zone Anycast Cloud 1 | ||||||
| PTR | ha2.markmonitor.zone | ||||||
| A | 162.219.54.170🇨🇦 CIRA-2162.219.54.0/24 D-Zone Anycast Cloud1 | ||||||
| PTR | ha2.markmonitor.zone | ||||||
| NS | ha3.markmonitor.zone | ||||||
| A | 2001:67c:10b8::5🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net | ||||||
| PTR | ha3.markmonitor.zone | ||||||
| A | 176.97.158.5🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net | ||||||
| PTR | ha3.markmonitor.zone | ||||||
| NS | ha4.markmonitor.zone | ||||||
| A | 2620:10a:80ec::6b🇨🇦 CIRA-32620:10a:80ec::/48 D-Zone IPv6 Anycast Cloud 2 | ||||||
| PTR | ha4.markmonitor.zone | ||||||
| A | 162.219.55.170🇨🇦 CIRA-3162.219.55.0/24 D-Zone Anycast Cloud 2 | ||||||
| PTR | ha4.markmonitor.zone | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ha1.markmonitor.zonehostmaster@markmonitor.com 2020-08-27 #1 | ||||||
community
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | v0n0.nic.community ⭐ | ||||||
| NS | v0n1.nic.community | ||||||
| NS | v0n2.nic.community | ||||||
| NS | v0n3.nic.community | ||||||
| NS | v2n0.nic.community | ||||||
| NS | v2n1.nic.community | ||||||
| SOA | v0n0.nic.communityhostmaster@donuts.email serial=1785672882 | ||||||
Same first word
Similar names
DNS History
10 records (4 active, 6 former)
●NSha1.markmonitor.zone2017-09-18 → 2026-08-02 · 3 obs
● 2017-09-18 02:27:24
● 2026-08-02 12:33:04
●NSha2.markmonitor.zone2017-09-18 → 2026-08-02 · 3 obs
● 2017-09-18 02:27:24
● 2026-08-02 12:33:04
●NSha3.markmonitor.zone2017-09-18 → 2026-08-02 · 3 obs
● 2017-09-18 02:27:24
● 2026-08-02 12:33:04
●NSha4.markmonitor.zone2017-09-18 → 2026-08-02 · 3 obs
● 2017-09-18 02:27:24
● 2026-08-02 12:33:04
○NSpdns1.ultradns.net2016-12-10 → 2016-12-10 · 3 obs
○ 2017-09-18 02:27:24
○ 2026-08-02 12:33:04
○NSpdns2.ultradns.net2016-12-10 → 2016-12-10 · 3 obs
○ 2017-09-18 02:27:24
○ 2026-08-02 12:33:04
○NSpdns3.ultradns.org2016-12-10 → 2016-12-10 · 3 obs
○ 2017-09-18 02:27:24
○ 2026-08-02 12:33:04
○NSpdns4.ultradns.org2016-12-10 → 2016-12-10 · 3 obs
○ 2017-09-18 02:27:24
○ 2026-08-02 12:33:04
○NSpdns5.ultradns.info2016-12-10 → 2016-12-10 · 3 obs
○ 2017-09-18 02:27:24
○ 2026-08-02 12:33:04
○NSpdns6.ultradns.co.uk2016-12-10 → 2016-12-10 · 3 obs
○ 2017-09-18 02:27:24
○ 2026-08-02 12:33:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| community | v0n2.nic.community, v0n3.nic.community, v2n0.nic.community, v2n1.nic.community... | 12 records |
| adp.community | ha1.markmonitor.zone, ha3.markmonitor.zone, ha2.markmonitor.zone, ha4.markmonitor.zone | - |
✅ Authoritative Response
Server:192.174.68.5
NS records: ha1.markmonitor.zone, ha3.markmonitor.zone, ha2.markmonitor.zone, ha4.markmonitor.zone
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for adp.community (unsigned zone)
⏱️ Timing
Total: 446ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ha1.markmonitor.zone, ha2.markmonitor.zone... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ha1.markmonitor.zone hostmaster.markmoni |
📌 Glue Records Collected
Total: 12
In-bailiwick: 12 (v2n1.nic.community, v2n0.nic.community, v0n3.nic.community...)
Analysis
Name Servers
adp.community has four authoritative name servers: ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone and ha4.markmonitor.zone.
There is at least partial name server overlap between adp.community and other domains — clarivateanalytics.com.hk, adpnetpay.com, rifampicin.info and two more among them.
These name servers regularly appear alongside ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com and 4 other name servers in NS record sets.
All four hostnames — ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone and ha4.markmonitor.zone — resolve to two IP numbers apiece: ha1.markmonitor.zone to 192.174.68.5 and 2001:67c:1bc::5; ha2.markmonitor.zone to 162.219.54.170 and 2620:10a:80eb::6b; ha3.markmonitor.zone to 176.97.158.5 and 2001:67c:10b8::5; ha4.markmonitor.zone to 162.219.55.170 and 2620:10a:80ec::6b.