halcomb.us - dns.ninja

`halcomb.us`

DNSSEC	⚠️ Not signed
A	108.24.138.23^{🇺🇸 AS701108.24.0.0/16 MCI Communications Services, LLC d/b/a Verizon Business}
		PTR	`pool-108-24-138-23.cmdnnj.fios.verizon.net`
NS	`ns77.domaincontrol.com` ⭐
		A	2603:5:21c4::31^{🇺🇸 GODADDY-DNS2603:5:21c0::/44}
			PTR	`ns77.domaincontrol.com`
		A	97.74.108.49^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns77.domaincontrol.com`
NS	`ns78.domaincontrol.com`
		A	2603:5:22c4::31^{🇺🇸 GODADDY-DNS2603:5:22c0::/44}
			PTR	`ns78.domaincontrol.com`
		A	173.201.76.49^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns78.domaincontrol.com`
MX	`alt1.aspmx.l.google.com` ⭐
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-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::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
SOA	`ns77.domaincontrol.com`dns@jomax.net 2025-10-24 #1

`us`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.cctld.us` ⭐
	NS	`b.cctld.us`
	NS	`f.cctld.us`
	NS	`k.cctld.us`
	NS	`m.cctld.us`
	NS	`n.cctld.us`
	NS	`w.cctld.us`
	NS	`x.cctld.us`
	NS	`y.cctld.us`
	SOA	`a.cctld.us`admin@tldns.godaddy serial=1785543095

Same first word

halcomb.com

halcomb.org

halcomb.us

Similar names

combahl.com

cholbam.com

molbach.no

hmcolab.com

molbach.com

abcholm.com

lachomb.com

combahl.cl

lombach.de

mbaloch.com

molbach.net

DNS History

18 records (7 active, 11 former)

○NSdns135.b.register.com2015-06-06 → 2017-04-10 · 4 obs

● 2015-06-06 12:19:06
● 2017-04-10 21:44:54
○ 2026-05-19 02:15:58
○ 2026-08-01 00:29:08

○NSdns160.a.register.com2015-06-06 → 2017-04-10 · 4 obs

● 2015-06-06 12:19:06
● 2017-04-10 21:44:54
○ 2026-05-19 02:15:58
○ 2026-08-01 00:29:08

○NSdns246.c.register.com2015-06-06 → 2017-04-10 · 4 obs

● 2015-06-06 12:19:06
● 2017-04-10 21:44:54
○ 2026-05-19 02:15:58
○ 2026-08-01 00:29:08

○NSdns249.d.register.com2015-06-06 → 2017-04-10 · 4 obs

● 2015-06-06 12:19:06
● 2017-04-10 21:44:54
○ 2026-05-19 02:15:58
○ 2026-08-01 00:29:08

●NSns77.domaincontrol.com2026-05-19 → 2026-08-01 · 3 obs

○ 2017-04-10 21:44:54
● 2026-05-19 02:15:58
● 2026-08-01 00:29:08

●NSns78.domaincontrol.com2026-05-19 → 2026-08-01 · 3 obs

○ 2017-04-10 21:44:54
● 2026-05-19 02:15:58
● 2026-08-01 00:29:08

●MXalt1.aspmx.l.google.com2015-06-06 → 2026-08-01 · 2 obs

● 2015-06-06 12:19:06
● 2026-08-01 00:29:08

●MXalt2.aspmx.l.google.com2015-06-06 → 2026-08-01 · 2 obs

● 2015-06-06 12:19:06
● 2026-08-01 00:29:08

●MXalt3.aspmx.l.google.com2026-05-19 → 2026-08-01 · 3 obs

○ 2017-04-10 21:44:54
● 2026-05-19 02:15:58
● 2026-08-01 00:29:08

●MXalt4.aspmx.l.google.com2026-05-19 → 2026-08-01 · 3 obs

○ 2017-04-10 21:44:54
● 2026-05-19 02:15:58
● 2026-08-01 00:29:08

○MXaspmx.l.google.com2015-06-06 → 2017-04-10 · 4 obs

● 2015-06-06 12:19:06
● 2017-04-10 21:44:54
○ 2026-05-19 02:15:58
○ 2026-08-01 00:29:08

○MXaspmx2.googlemail.com2015-06-06 → 2017-04-10 · 4 obs

● 2015-06-06 12:19:06
● 2017-04-10 21:44:54
○ 2026-05-19 02:15:58
○ 2026-08-01 00:29:08

○MXaspmx3.googlemail.com2015-06-06 → 2017-04-10 · 4 obs

● 2015-06-06 12:19:06
● 2017-04-10 21:44:54
○ 2026-05-19 02:15:58
○ 2026-08-01 00:29:08

○MXaspmx4.googlemail.com2015-06-06 → 2017-04-10 · 4 obs

● 2015-06-06 12:19:06
● 2017-04-10 21:44:54
○ 2026-05-19 02:15:58
○ 2026-08-01 00:29:08

○MXaspmx5.googlemail.com2015-06-06 → 2017-04-10 · 4 obs

● 2015-06-06 12:19:06
● 2017-04-10 21:44:54
○ 2026-05-19 02:15:58
○ 2026-08-01 00:29:08

○A108.24.129.1912017-04-10 → 2017-04-10 · 4 obs

○ 2016-09-29 15:52:48
● 2017-04-10 21:44:54
○ 2026-05-19 02:15:58
○ 2026-08-01 00:29:08

●A108.24.138.232026-05-19 → 2026-08-01 · 3 obs

○ 2017-04-10 21:44:54
● 2026-05-19 02:15:58
● 2026-08-01 00:29:08

○A67.241.68.1792015-06-06 → 2016-09-29 · 4 obs

● 2015-06-06 12:19:06
● 2016-09-29 15:52:48
○ 2017-04-10 21:44:54
○ 2026-08-01 00:29:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
us	b.cctld.us, f.cctld.us, k.cctld.us, m.cctld.us...	-
halcomb.us	ns77.domaincontrol.com, ns78.domaincontrol.com	-

✅ Authoritative Response

Server:173.201.76.49

NS records: ns77.domaincontrol.com, ns78.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for halcomb.us (unsigned zone)

⏱️ Timing

Total: 573ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`108.24.138.23`
NS	2	`ns77.domaincontrol.com, ns78.domaincontrol.com`
MX	4	`alt3.aspmx.l.google.com (pri: 10), alt4.aspmx.l.google.com (pri: 10)...`
SOA	1	`ns77.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

halcomb.us resolves to just one IP address, 108.24.138.23.

Among the host names that share IP numbers with halcomb.us is pool-108-24-138-23.cmdnnj.fios.verizon.net, as one example.

Name Servers

The NS records for halcomb.us delegate to ns77.domaincontrol.com and ns78.domaincontrol.com.

halcomb.us shares its NS records with other domains, for example wasatchpipeandsuply.com, onlinesoccerschool.com, svenskt-casino-utan-licens.com and two others.

ns77.domaincontrol.com resolves to 97.74.108.49 and 2603:5:21c4::31. Likewise, ns78.domaincontrol.com resolves to 173.201.76.49 and 2603:5:22c4::31 — two IP addresses apiece.

Mail Servers

Mail for halcomb.us is handled by four mail servers: alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

There is at least a partial MX overlap between halcomb.us and other domains, including ns500742.ns500754.ns500731.ns500704.ns500671.ns500731.ns500688.ns500705.ns500671.ns500291.ns500678.ns500666.ns500653.ns500153.tenderladiesbz.com, ns500754.ns500731.ns500671.ns500742.ns500671.ns500705.ns500705.ns500688.ns500678.ns500671.ns500704.ns500705.ns500678.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500734.ns500693.ns500699.ns500734.ns500693.ns500699.ns500699.ns500693.ns500588.ns500699.ns500693.ns500693.ns500588.ns500683.ns500699.ns500612.ns500110.dtrkdll.com and two others.

These mail servers frequently co-occur with the mail servers aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com and two others.

All four hostnames — alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com — resolve to two IP numbers apiece: alt1.aspmx.l.google.com to 108.177.123.27 and 2800:3f0:4003:c0f::1a; alt2.aspmx.l.google.com to 172.253.116.27 and 2a00:1450:400b:c02::1a; alt3.aspmx.l.google.com to 192.178.223.26 and 2a00:1450:4009:c0f::1a; alt4.aspmx.l.google.com to 172.253.157.27 and 2a00:1450:400c:c23::1b.