🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`code-violation.com`

DNSSEC	⚠️ Not signed
A	192.0.78.24^{🇺🇸 Automattic192.0.78.0/24 Route Object}
A	192.0.78.25^{🇺🇸 Automattic192.0.78.0/24 Route Object}
NS	`ns29.domaincontrol.com` ⭐
		A	2603:5:2181::f^{🇺🇸 GODADDY-DNS2603:5:2180::/44}
			PTR	`ns29.domaincontrol.com`
		A	97.74.104.15^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns29.domaincontrol.com`
NS	`ns30.domaincontrol.com`
		A	2603:5:2281::f^{🇺🇸 GODADDY-DNS2603:5:2280::/44}
			PTR	`ns30.domaincontrol.com`
		A	173.201.72.15^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns30.domaincontrol.com`
MX	`codeviolation-com01b.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c946::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch4pr04cu00102.inbound.protection.outlook.com`
		A	2a01:111:f403:f802::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr05cu00400.inbound.protection.outlook.com`
		A	2a01:111:f403:f802::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:f804::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr05cu00402.inbound.protection.outlook.com`
		A	52.101.60.160^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn0pr04cu00800.inbound.protection.outlook.com`
		A	52.101.194.3^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch1pr04cu00103.inbound.protection.outlook.com`
		A	52.101.194.4^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch4pr04cu00104.inbound.protection.outlook.com`
		A	52.101.194.17^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch5pr02cu00401.inbound.protection.outlook.com`
TXT	`NETORGFT16039029.onmicrosoft.com`
TXT	`v=spf1 include:secureserver.net -all`
SOA	`ns29.domaincontrol.com`dns@jomax.net 2024-04-08 #0

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

Same first word

code-violation.com

Previous names

Next names

DNS History

12 records (5 active, 7 former)

○NSns0.phase8.net2015-07-22 → 2019-04-25 · 4 obs

● 2015-07-22 16:07:22
● 2019-04-25 23:47:38
○ 2026-09-02 07:11:46
○ 2026-09-07 07:58:54

○NSns1.phase8.net2015-07-22 → 2019-04-25 · 4 obs

● 2015-07-22 16:07:22
● 2019-04-25 23:47:38
○ 2026-09-02 07:11:46
○ 2026-09-07 07:58:54

○NSns2.phase8.net2015-07-22 → 2019-04-25 · 4 obs

● 2015-07-22 16:07:22
● 2019-04-25 23:47:38
○ 2026-09-02 07:11:46
○ 2026-09-07 07:58:54

●NSns29.domaincontrol.com2026-09-02 → 2026-09-07 · 3 obs

○ 2019-04-25 23:47:38
● 2026-09-02 07:11:46
● 2026-09-07 07:58:54

●NSns30.domaincontrol.com2026-09-02 → 2026-09-07 · 3 obs

○ 2019-04-25 23:47:38
● 2026-09-02 07:11:46
● 2026-09-07 07:58:54

●MXcodeviolation-com01b.mail.protection.outlook.com2026-09-02 → 2026-09-07 · 3 obs

○ 2019-04-25 23:47:38
● 2026-09-02 07:11:46
● 2026-09-07 07:58:54

○MXfwd0.hosts.co.uk2015-07-22 → 2019-04-25 · 4 obs

● 2015-07-22 16:07:22
● 2019-04-25 23:47:38
○ 2026-09-02 07:11:46
○ 2026-09-07 07:58:54

○MXfwd1.hosts.co.uk2015-07-22 → 2019-04-25 · 4 obs

● 2015-07-22 16:07:22
● 2019-04-25 23:47:38
○ 2026-09-02 07:11:46
○ 2026-09-07 07:58:54

○MXfwd2.hosts.co.uk2015-07-22 → 2019-04-25 · 4 obs

● 2015-07-22 16:07:22
● 2019-04-25 23:47:38
○ 2026-09-02 07:11:46
○ 2026-09-07 07:58:54

●A192.0.78.242026-09-02 → 2026-09-07 · 3 obs

○ 2019-04-25 23:47:38
● 2026-09-02 07:11:46
● 2026-09-07 07:58:54

●A192.0.78.252026-09-02 → 2026-09-07 · 3 obs

○ 2019-04-25 23:47:38
● 2026-09-02 07:11:46
● 2026-09-07 07:58:54

○A85.233.160.222015-07-22 → 2019-04-25 · 4 obs

● 2015-07-22 16:07:22
● 2019-04-25 23:47:38
○ 2026-09-02 07:11:46
○ 2026-09-07 07:58:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
code-violation.com	ns29.domaincontrol.com, ns30.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.104.15

NS records: ns29.domaincontrol.com, ns30.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for code-violation.com (unsigned zone)

⏱️ Timing

Total: 158ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`192.0.78.24, 192.0.78.25`
NS	2	`ns29.domaincontrol.com, ns30.domaincontrol.com`
MX	1	`codeviolation-com01b.mail.protection.out`
TXT	2	`NETORGFT16039029.onmicrosoft.com, v=spf1 include:secureserver.net -all`
SOA	1	`ns29.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns29.domaincontrol.com, ns29.domaincontrol.com, ns30.domaincontrol.com...)

Analysis

IP Addresses

code-violation.com has two IP addresses: 192.0.78.24 and 192.0.78.25

iwanttoknowwhattodonowthatiamsaved.org, ourcarolinapromise.com, zorro-veranatura.com and two other host names share IP numbers with code-violation.com.

Name Servers

code-violation.com is served by two delegated name servers, ns29.domaincontrol.com and ns30.domaincontrol.com.

code-violation.com uses the same name servers as several other domains — among them agrivers.ai, novelwritingintensive.org, lapredireprestigeparis.com and two more.

The DNS delegation for code-violation.com at least partly coincides with that of other domains, cfhshl.com being one example.

Each of the two host names carries two IP addresses: ns29.domaincontrol.com points to 97.74.104.15 and 2603:5:2181::f, and ns30.domaincontrol.com points to 173.201.72.15 and 2603:5:2281::f.

Mail Servers

Mail for code-violation.com is handled by a single mail server, codeviolation-com01b.mail.protection.outlook.com.

codeviolation-com01b.mail.protection.outlook.com resolves to 8 IP addresses — 52.101.60.160, 52.101.194.3, 52.101.194.4 and 5 others.

code-violation.com - robtex.com