`dccmonitoring.com`

DNSSEC	⚠️ Not signed
A	3.33.251.168^{🇺🇸 Amazon3.33.240.0/20}
		PTR	`aec037177372cc6cd.awsglobalaccelerator.com`
A	15.197.225.128^{🇺🇸 Amazon15.197.224.0/20}
NS	`ns35.domaincontrol.com` ⭐
		A	2603:5:21b1::12^{🇺🇸 GODADDY-DNS2603:5:21b0::/44}
			PTR	`ns35.domaincontrol.com`
		A	97.74.107.18^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns35.domaincontrol.com`
NS	`ns36.domaincontrol.com`
		A	2603:5:22b1::12^{🇺🇸 GODADDY-DNS2603:5:22b0::/44}
			PTR	`ns36.domaincontrol.com`
		A	173.201.75.18^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns36.domaincontrol.com`
SOA	`ns35.domaincontrol.com`dns@jomax.net 2026-02-17 #3

`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.net`nstld@verisign-grs.com serial=1774720842

Previously MX for

dccmonitoring.com

Same first word

dccmonitoring.com

DNS History

9 records (4 active, 5 former)

○NSns1.digitalocean.com2018-05-15 → 2018-05-15 · 3 obs

● 2018-05-15 03:08:34
○ 2026-03-27 11:19:14
○ 2026-03-28 18:03:58

○NSns2.digitalocean.com2018-05-15 → 2018-05-15 · 3 obs

● 2018-05-15 03:08:34
○ 2026-03-27 11:19:14
○ 2026-03-28 18:03:58

○NSns3.digitalocean.com2018-05-15 → 2018-05-15 · 3 obs

● 2018-05-15 03:08:34
○ 2026-03-27 11:19:14
○ 2026-03-28 18:03:58

●NSns35.domaincontrol.com2026-03-27 → 2026-03-28 · 3 obs

○ 2018-05-15 03:08:34
● 2026-03-27 11:19:14
● 2026-03-28 18:03:58

●NSns36.domaincontrol.com2026-03-27 → 2026-03-28 · 3 obs

○ 2018-05-15 03:08:34
● 2026-03-27 11:19:14
● 2026-03-28 18:03:58

○MXdccmonitoring.com2018-05-15 → 2018-05-15 · 3 obs

● 2018-05-15 03:08:34
○ 2026-03-27 11:19:14
○ 2026-03-28 18:03:58

●A15.197.225.1282026-03-27 → 2026-03-28 · 3 obs

○ 2018-05-15 03:08:34
● 2026-03-27 11:19:14
● 2026-03-28 18:03:58

○A159.65.174.1472018-05-15 → 2018-05-15 · 3 obs

● 2018-05-15 03:08:34
○ 2026-03-27 11:19:14
○ 2026-03-28 18:03:58

●A3.33.251.1682026-03-27 → 2026-03-28 · 3 obs

○ 2018-05-15 03:08:34
● 2026-03-27 11:19:14
● 2026-03-28 18:03:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, a.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net...	-
dccmonitoring.com	ns35.domaincontrol.com, ns36.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.75.18

NS records: ns35.domaincontrol.com, ns36.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for dccmonitoring.com (unsigned zone)

⏱️ Timing

Total: 113ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`15.197.225.128, 3.33.251.168`
NS	2	`ns35.domaincontrol.com, ns36.domaincontrol.com`
SOA	1	`ns35.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns35.domaincontrol.com, ns35.domaincontrol.com, ns36.domaincontrol.com...)

Analysis

IP Addresses

dccmonitoring.com points to two IP numbers: 3.33.251.168 and 15.197.225.128.

Other host names, for instance floridalicensedplumber.com, fit-180.com, venthead.com, height-safety.co.uk and kantomeal.com share IP numbers with dccmonitoring.com.

Name Servers

dccmonitoring.com's delegation is to two name servers ns35.domaincontrol.com and ns36.domaincontrol.com.

dccmonitoring.com shares the same name server configuration as other domains, such as mailyourmark.com, rfsinc.net, atowers.net, investarizona.com and gas-worldwide.us.

dccmonitoring.com shares name servers with other domains at least partially, for example vandelk.com.

Host names with two IP numbers: ns35.domaincontrol.com points to 2603:5:21b1::12 and 97.74.107.18; ns36.domaincontrol.com points to 2603:5:22b1::12 and 173.201.75.18

dccmonitoring.com - robtex.com