🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`code-huddle.com`

DNSSEC	⚠️ Not signed
A	216.150.1.1^{🇨🇦 Amazon216.150.1.0/24 EC2 Prefix}
NS	`ns09.domaincontrol.com` ⭐
		A	2603:5:2180::5^{🇺🇸 GODADDY-DNS2603:5:2180::/44}
			PTR	`ns09.domaincontrol.com`
		A	97.74.104.5^{🇺🇸 GODADDY-DNS97.74.104.0/23}
			PTR	`ns09.domaincontrol.com`
NS	`ns10.domaincontrol.com`
		A	2603:5:2280::5^{🇺🇸 GODADDY-DNS2603:5:2280::/44}
			PTR	`ns10.domaincontrol.com`
		A	173.201.72.5^{🇺🇸 GODADDY-DNS173.201.72.0/23}
			PTR	`ns10.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c25::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f26.1e100.net`
		A	142.250.31.26^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.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.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 include:dc-aa8e722993._spfm.code-huddle.com ~all`
SOA	`ns09.domaincontrol.com`dns@jomax.net 2026-07-14 #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=1787995280

Same first word

code-huddle.com

Previous names

Next names

DNS History

14 records (8 active, 6 former)

●NSns09.domaincontrol.com2026-08-23 → 2026-08-29 · 3 obs

○ 2017-06-19 07:42:52
● 2026-08-23 05:32:26
● 2026-08-29 09:35:54

○NSns1.pine.arvixe.com2015-08-04 → 2017-06-19 · 4 obs

● 2015-08-04 01:16:52
● 2017-06-19 07:42:52
○ 2026-08-23 05:32:26
○ 2026-08-29 09:35:54

●NSns10.domaincontrol.com2026-08-23 → 2026-08-29 · 3 obs

○ 2017-06-19 07:42:52
● 2026-08-23 05:32:26
● 2026-08-29 09:35:54

○NSns2.pine.arvixe.com2015-08-04 → 2017-06-19 · 4 obs

● 2015-08-04 01:16:52
● 2017-06-19 07:42:52
○ 2026-08-23 05:32:26
○ 2026-08-29 09:35:54

●MXalt1.aspmx.l.google.com2026-08-23 → 2026-08-29 · 3 obs

○ 2017-06-19 07:42:52
● 2026-08-23 05:32:26
● 2026-08-29 09:35:54

●MXalt2.aspmx.l.google.com2026-08-23 → 2026-08-29 · 3 obs

○ 2017-06-19 07:42:52
● 2026-08-23 05:32:26
● 2026-08-29 09:35:54

●MXalt3.aspmx.l.google.com2026-08-23 → 2026-08-29 · 3 obs

○ 2017-06-19 07:42:52
● 2026-08-23 05:32:26
● 2026-08-29 09:35:54

●MXalt4.aspmx.l.google.com2026-08-23 → 2026-08-29 · 3 obs

○ 2017-06-19 07:42:52
● 2026-08-23 05:32:26
● 2026-08-29 09:35:54

●MXaspmx.l.google.com2026-08-23 → 2026-08-29 · 3 obs

○ 2017-06-19 07:42:52
● 2026-08-23 05:32:26
● 2026-08-29 09:35:54

○MXmail.code-huddle.com2015-08-04 → 2017-06-19 · 4 obs

● 2015-08-04 01:16:52
● 2017-06-19 07:42:52
○ 2026-08-23 05:32:26
○ 2026-08-29 09:35:54

○MXmail2.code-huddle.com2015-08-04 → 2017-06-19 · 4 obs

● 2015-08-04 01:16:52
● 2017-06-19 07:42:52
○ 2026-08-23 05:32:26
○ 2026-08-29 09:35:54

○A143.95.252.462015-11-28 → 2017-06-19 · 5 obs

○ 2015-08-04 01:16:52
● 2015-11-28 21:39:18
● 2017-06-19 07:42:52
○ 2026-08-23 05:32:26
○ 2026-08-29 09:35:54

●A216.150.1.12026-08-23 → 2026-08-29 · 3 obs

○ 2017-06-19 07:42:52
● 2026-08-23 05:32:26
● 2026-08-29 09:35:54

○A23.91.123.482015-08-04 → 2015-08-04 · 3 obs

● 2015-08-04 01:16:52
○ 2015-11-28 21:39:18
○ 2026-08-29 09:35:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, m.gtld-servers.net, a.gtld-servers.net, c.gtld-servers.net...	-
code-huddle.com	ns09.domaincontrol.com, ns10.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.104.5

NS records: ns09.domaincontrol.com, ns10.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

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

⏱️ Timing

Total: 2054ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.150.1.1`
NS	2	`ns10.domaincontrol.com, ns09.domaincontrol.com`
MX	5	`alt4.aspmx.l.google.com (pri: 10), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 include:dc-aa8e722993._spfm.code-`
SOA	1	`ns09.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns09.domaincontrol.com, ns09.domaincontrol.com, ns10.domaincontrol.com...)

Analysis

IP Addresses

code-huddle.com resolves to one IP address: 216.150.1.1.

woanstudios.com, nextstage.io, bookstruck.in and two other host names share IP numbers with code-huddle.com.

Name Servers

code-huddle.com has two authoritative name servers — ns09.domaincontrol.com and ns10.domaincontrol.com.

code-huddle.com uses the same name servers as several other domains — among them seo-moto.de, heyven.net, rezencore.email and two more.

Both ns09.domaincontrol.com and ns10.domaincontrol.com have two IP addresses each. ns09.domaincontrol.com resolves to 97.74.104.5 and 2603:5:2180::5; ns10.domaincontrol.com resolves to 173.201.72.5 and 2603:5:2280::5.

Mail Servers

Mail for code-huddle.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

code-huddle.com has at least partial mail server overlap with other domains such as ihaletakip.com.tr, sljcoaching.com, disl.edu and two more.

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

Hostnames that resolve to two IP addresses:

aspmx.l.google.com resolves to 142.250.31.26 and 2607:f8b0:4004:c25::1a.

alt1.aspmx.l.google.com resolves to 192.178.234.27 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1a.