🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`codingcops.com`

DNSSEC	⚠️ Not signed
A	54.186.216.139^{🇺🇸 Amazon54.186.0.0/15 EC2 PDX prefix}
		PTR	`ec2-54-186-216-139.us-west-2.compute.amazonaws.com`
A	100.22.52.16^{🇺🇸 Amazon100.20.0.0/14 EC2 PDX prefix}
NS	`ns-172.awsdns-21.com` ⭐
		A	2600:9000:5300:ac00::1^{🇺🇸 Amazon2600:9000:5300::/48 - CloudFront}
			PTR	`ns-172.awsdns-21.com`
		A	205.251.192.172^{🇺🇸 Amazon205.251.192.0/24 prefix}
			PTR	`ns-172.awsdns-21.com`
NS	`ns-1256.awsdns-29.org`
		A	2600:9000:5304:e800::1^{🇺🇸 Amazon2600:9000:5304::/48 - CloudFront}
			PTR	`ns-1256.awsdns-29.org`
		A	205.251.196.232^{🇺🇸 Amazon205.251.196.0/24 prefix}
			PTR	`ns-1256.awsdns-29.org`
NS	`ns-1764.awsdns-28.co.uk`
		A	2600:9000:5306:e400::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1764.awsdns-28.co.uk`
		A	205.251.198.228^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1764.awsdns-28.co.uk`
NS	`ns-891.awsdns-47.net`
		A	2600:9000:5303:7b00::1^{🇺🇸 Amazon2600:9000:5303::/48 - CloudFront}
			PTR	`ns-891.awsdns-47.net`
		A	205.251.195.123^{🇺🇸 Amazon205.251.195.0/24 prefix}
			PTR	`ns-891.awsdns-47.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c08::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bi-in-f27.1e100.net`
		A	192.178.218.27^{🇺🇸 Google192.178.218.0/24}
			PTR	`yuiadtq-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`google-site-verification=kSdJ(0x787878)zDt3SLAdiJODY-KB3i61FGlINcoOLZOpib1M`
TXT	`v=spf1 include:_spf.google.com include:amazonses.com -all`
SOA	`ns-172.awsdns-21.com`awsdns-hostmaster@amazon.com serial=1

`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=1787898680

rank #858000 globally
rank #358944 in the tld

Same first word

codingcops.com

codingcops.site

codingcops.me

Similar names

codingscop.live

Previous names

Next names

DNS History

28 records (11 active, 17 former)

○NSdns1.name-services.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 19:15:46
○ 2015-10-20 19:57:16
○ 2026-08-28 06:42:46

○NSdns2.name-services.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 19:15:46
○ 2015-10-20 19:57:16
○ 2026-08-28 06:42:46

○NSdns3.name-services.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 19:15:46
○ 2015-10-20 19:57:16
○ 2026-08-28 06:42:46

○NSdns4.name-services.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 19:15:46
○ 2015-10-20 19:57:16
○ 2026-08-28 06:42:46

○NSdns5.name-services.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 19:15:46
○ 2015-10-20 19:57:16
○ 2026-08-28 06:42:46

●NSns-1256.awsdns-29.org2026-03-07 → 2026-08-28 · 3 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
● 2026-08-28 06:42:46

●NSns-172.awsdns-21.com2026-03-07 → 2026-08-28 · 3 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
● 2026-08-28 06:42:46

●NSns-1764.awsdns-28.co.uk2026-03-07 → 2026-08-28 · 3 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
● 2026-08-28 06:42:46

●NSns-891.awsdns-47.net2026-03-07 → 2026-08-28 · 3 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
● 2026-08-28 06:42:46

○NSns67.domaincontrol.com2016-09-20 → 2017-06-25 · 5 obs

○ 2015-10-20 19:57:16
● 2016-09-20 09:36:18
● 2017-06-25 16:16:24
○ 2026-03-07 03:30:24
○ 2026-08-28 06:42:46

○NSns68.domaincontrol.com2016-09-20 → 2017-06-25 · 5 obs

○ 2015-10-20 19:57:16
● 2016-09-20 09:36:18
● 2017-06-25 16:16:24
○ 2026-03-07 03:30:24
○ 2026-08-28 06:42:46

●MXalt1.aspmx.l.google.com2026-03-07 → 2026-08-28 · 3 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
● 2026-08-28 06:42:46

●MXalt2.aspmx.l.google.com2026-03-07 → 2026-08-28 · 3 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
● 2026-08-28 06:42:46

●MXalt3.aspmx.l.google.com2026-03-07 → 2026-08-28 · 3 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
● 2026-08-28 06:42:46

●MXalt4.aspmx.l.google.com2026-03-07 → 2026-08-28 · 3 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
● 2026-08-28 06:42:46

●MXaspmx.l.google.com2026-03-07 → 2026-08-28 · 3 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
● 2026-08-28 06:42:46

○MXmailstore1.secureserver.net2016-09-20 → 2017-06-25 · 4 obs

● 2016-09-20 09:36:18
● 2017-06-25 16:16:24
○ 2026-03-07 03:30:24
○ 2026-08-28 06:42:46

○MXsmtp.secureserver.net2016-09-20 → 2017-06-25 · 4 obs

● 2016-09-20 09:36:18
● 2017-06-25 16:16:24
○ 2026-03-07 03:30:24
○ 2026-08-28 06:42:46

●A100.22.52.162026-08-20 → 2026-08-28 · 3 obs

○ 2026-07-19 16:16:30
● 2026-08-20 03:15:00
● 2026-08-28 06:42:46

○A16.147.110.902026-05-06 → 2026-05-06 · 4 obs

○ 2026-03-07 03:30:24
● 2026-05-06 20:24:24
○ 2026-07-19 16:16:30
○ 2026-08-28 06:42:46

○A35.163.54.572026-03-07 → 2026-03-07 · 4 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
○ 2026-05-06 20:24:24
○ 2026-08-28 06:42:46

○A35.164.180.842026-07-19 → 2026-07-19 · 4 obs

○ 2026-05-06 20:24:24
● 2026-07-19 16:16:30
○ 2026-08-20 03:15:00
○ 2026-08-28 06:42:46

○A44.247.131.462026-05-06 → 2026-05-06 · 4 obs

○ 2026-03-07 03:30:24
● 2026-05-06 20:24:24
○ 2026-07-19 16:16:30
○ 2026-08-28 06:42:46

○A50.63.202.582016-09-20 → 2017-06-25 · 5 obs

○ 2015-10-20 19:57:16
● 2016-09-20 09:36:18
● 2017-06-25 16:16:24
○ 2026-03-07 03:30:24
○ 2026-08-28 06:42:46

○A52.25.95.1902026-03-07 → 2026-03-07 · 4 obs

○ 2017-06-25 16:16:24
● 2026-03-07 03:30:24
○ 2026-05-06 20:24:24
○ 2026-08-28 06:42:46

○A54.148.158.2522026-07-19 → 2026-07-19 · 4 obs

○ 2026-05-06 20:24:24
● 2026-07-19 16:16:30
○ 2026-08-20 03:15:00
○ 2026-08-28 06:42:46

●A54.186.216.1392026-08-20 → 2026-08-28 · 3 obs

○ 2026-07-19 16:16:30
● 2026-08-20 03:15:00
● 2026-08-28 06:42:46

○A8.15.231.1312008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 19:15:46
○ 2015-10-20 19:57:16
○ 2026-08-28 06:42:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
codingcops.com	ns-172.awsdns-21.com, ns-891.awsdns-47.net, ns-1764.awsdns-28.co.uk, ns-1256.awsdns-29.org	2 records

✅ Authoritative Response

Server:205.251.192.172

NS records: ns-172.awsdns-21.com, ns-891.awsdns-47.net, ns-1764.awsdns-28.co.uk, ns-1256.awsdns-29.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for codingcops.com (unsigned zone)

⏱️ Timing

Total: 471ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`100.22.52.16, 54.186.216.139`
NS	4	`ns-1256.awsdns-29.org, ns-172.awsdns-21.com...`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`google-site-verification=kSdJ(0x787878)zDt3SLAd, v=spf1 include:_spf.google.com include:a`
SOA	1	`ns-172.awsdns-21.com awsdns-hostmaster.a`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns-172.awsdns-21.com, ns-172.awsdns-21.com)

Analysis

IP Addresses

codingcops.com points to the IP addresses 54.186.216.139 and 100.22.52.16

Other host names share IP numbers with codingcops.com; ec2-54-186-216-139.us-west-2.compute.amazonaws.com is one such example.

Name Servers

The authoritative name servers for codingcops.com are ns-172.awsdns-21.com, ns-891.awsdns-47.net, ns-1256.awsdns-29.org and ns-1764.awsdns-28.co.uk.

The name servers of codingcops.com overlap at least partially with those of other domains — among them ims.io, d2q5qux0jpombq.cloudfront.net, independencelenders.com and two more.

The name servers ns-1244.awsdns-27.org, ns-298.awsdns-37.com and ns-1880.awsdns-43.co.uk are commonly seen alongside these name servers.

Each of the four hosts ns-172.awsdns-21.com, ns-891.awsdns-47.net, ns-1256.awsdns-29.org and ns-1764.awsdns-28.co.uk has two IP addresses. ns-172.awsdns-21.com points to 205.251.192.172 and 2600:9000:5300:ac00::1. ns-891.awsdns-47.net points to 205.251.195.123 and 2600:9000:5303:7b00::1. ns-1256.awsdns-29.org points to 205.251.196.232 and 2600:9000:5304:e800::1. ns-1764.awsdns-28.co.uk points to 205.251.198.228 and 2600:9000:5306:e400::1.

Mail Servers

codingcops.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

codingcops.com has at least partial mail server overlap with other domains such as curzioresearch.com, caparchment.com, carrolltaxfirm.com and two more.

These mail servers commonly co-occur with mail servers alt4.aspmx.l.google.com, alt3.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com maps to two IP addresses — 192.178.218.27 and 2607:f8b0:4004:c08::1b.

alt1.aspmx.l.google.com maps to two IP addresses — 192.178.234.26 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.27 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.26 and 2a00:1450:400c:c23::1a.