securehhc.com - dns.ninja

`securehhc.com`

DNSSEC	⚠️ Not signed
A	107.180.113.95^{🇺🇸 AS398101107.180.112.0/22}
		PTR	`95.113.180.107.host.secureserver.net`
NS	`ns53.domaincontrol.com` ⭐
		A	2603:5:21a2::1b^{🇺🇸 GODADDY-DNS2603:5:21a0::/44}
			PTR	`ns53.domaincontrol.com`
		A	97.74.106.27^{🇺🇸 GODADDY-DNS97.74.106.0/23}
			PTR	`ns53.domaincontrol.com`
NS	`ns54.domaincontrol.com`
		A	2603:5:22a2::1b^{🇺🇸 GODADDY-DNS2603:5:22a0::/44}
			PTR	`ns54.domaincontrol.com`
		A	173.201.74.27^{🇺🇸 GODADDY-DNS173.201.74.0/23}
			PTR	`ns54.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.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: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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.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:_spf.google.com ~all`
SOA	`ns53.domaincontrol.com`dns@jomax.net 2024-05-22 #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=1785087567

Previously MX for

securehhc.com

Same first word

securehhc.com

Similar names

echurches.org

scheucher.org

scheucher.info

scheucher.com

cuhscheer.com

scheucher.eu

scheucher.us

echurches.com

scheucher.kz

scheucher.ch

scheucher.ru

scheucher.de

hhcsecure.com

scheucher.net

scheucher.at

DNS History

22 records (8 active, 14 former)

○NSdns1.name-services.com2019-02-28 → 2019-02-28 · 4 obs

○ 2017-02-13 20:43:18
● 2019-02-28 07:23:12
○ 2026-03-26 20:26:20
○ 2026-07-26 17:53:40

○NSdns2.name-services.com2019-02-28 → 2019-02-28 · 4 obs

○ 2017-02-13 20:43:18
● 2019-02-28 07:23:12
○ 2026-03-26 20:26:20
○ 2026-07-26 17:53:40

○NSdns3.name-services.com2019-02-28 → 2019-02-28 · 4 obs

○ 2017-02-13 20:43:18
● 2019-02-28 07:23:12
○ 2026-03-26 20:26:20
○ 2026-07-26 17:53:40

○NSdns4.name-services.com2019-02-28 → 2019-02-28 · 4 obs

○ 2017-02-13 20:43:18
● 2019-02-28 07:23:12
○ 2026-03-26 20:26:20
○ 2026-07-26 17:53:40

○NSdns5.name-services.com2019-02-28 → 2019-02-28 · 4 obs

○ 2017-02-13 20:43:18
● 2019-02-28 07:23:12
○ 2026-03-26 20:26:20
○ 2026-07-26 17:53:40

○NSns1.amanihost.com2015-08-04 → 2017-02-13 · 4 obs

● 2015-08-04 21:36:40
● 2017-02-13 20:43:18
○ 2019-02-28 07:23:12
○ 2026-07-26 17:53:40

○NSns1.websitehostserver.net2015-08-04 → 2017-02-13 · 4 obs

● 2015-08-04 21:36:40
● 2017-02-13 20:43:18
○ 2019-02-28 07:23:12
○ 2026-07-26 17:53:40

○NSns2.amanihost.com2015-08-04 → 2017-02-13 · 4 obs

● 2015-08-04 21:36:40
● 2017-02-13 20:43:18
○ 2019-02-28 07:23:12
○ 2026-07-26 17:53:40

○NSns2.websitehostserver.net2015-08-04 → 2017-02-13 · 4 obs

● 2015-08-04 21:36:40
● 2017-02-13 20:43:18
○ 2019-02-28 07:23:12
○ 2026-07-26 17:53:40

●NSns53.domaincontrol.com2026-03-26 → 2026-07-26 · 3 obs

○ 2019-02-28 07:23:12
● 2026-03-26 20:26:20
● 2026-07-26 17:53:40

●NSns54.domaincontrol.com2026-03-26 → 2026-07-26 · 3 obs

○ 2019-02-28 07:23:12
● 2026-03-26 20:26:20
● 2026-07-26 17:53:40

●MXalt1.aspmx.l.google.com2015-08-04 → 2026-07-26 · 2 obs

● 2015-08-04 21:36:40
● 2026-07-26 17:53:40

●MXalt2.aspmx.l.google.com2015-08-04 → 2026-07-26 · 2 obs

● 2015-08-04 21:36:40
● 2026-07-26 17:53:40

●MXalt3.aspmx.l.google.com2019-02-28 → 2026-07-26 · 3 obs

○ 2017-02-13 20:43:18
● 2019-02-28 07:23:12
● 2026-07-26 17:53:40

●MXalt4.aspmx.l.google.com2019-02-28 → 2026-07-26 · 3 obs

○ 2017-02-13 20:43:18
● 2019-02-28 07:23:12
● 2026-07-26 17:53:40

●MXaspmx.l.google.com2015-08-04 → 2026-07-26 · 2 obs

● 2015-08-04 21:36:40
● 2026-07-26 17:53:40

○MXaspmx2.googlemail.com2015-08-04 → 2017-02-13 · 4 obs

● 2015-08-04 21:36:40
● 2017-02-13 20:43:18
○ 2019-02-28 07:23:12
○ 2026-07-26 17:53:40

○MXaspmx3.googlemail.com2015-08-04 → 2017-02-13 · 4 obs

● 2015-08-04 21:36:40
● 2017-02-13 20:43:18
○ 2019-02-28 07:23:12
○ 2026-07-26 17:53:40

○MXsecurehhc.com2015-08-04 → 2017-02-13 · 4 obs

● 2015-08-04 21:36:40
● 2017-02-13 20:43:18
○ 2019-02-28 07:23:12
○ 2026-07-26 17:53:40

●A107.180.113.952026-03-26 → 2026-07-26 · 3 obs

○ 2019-02-28 07:23:12
● 2026-03-26 20:26:20
● 2026-07-26 17:53:40

○A184.154.126.1302015-08-04 → 2017-02-13 · 4 obs

● 2015-08-04 21:36:40
● 2017-02-13 20:43:18
○ 2019-02-28 07:23:12
○ 2026-07-26 17:53:40

○A98.124.251.1772019-02-28 → 2019-02-28 · 4 obs

○ 2017-02-13 20:43:18
● 2019-02-28 07:23:12
○ 2026-03-26 20:26:20
○ 2026-07-26 17:53:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
securehhc.com	ns53.domaincontrol.com, ns54.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.106.27

NS records: ns53.domaincontrol.com, ns54.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securehhc.com (unsigned zone)

⏱️ Timing

Total: 119ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`107.180.113.95`
NS	2	`ns53.domaincontrol.com, ns54.domaincontrol.com`
MX	5	`alt2.aspmx.l.google.com (pri: 5), alt4.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
SOA	1	`ns53.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns53.domaincontrol.com, ns53.domaincontrol.com, ns54.domaincontrol.com...)

Analysis

IP Addresses

securehhc.com resolves to just one IP address, 107.180.113.95.

Two other host names, along with saisservices.com, mail.take2design.info and rtclogistics.in, also share IP numbers with securehhc.com.

Name Servers

Two name servers handle the delegation for securehhc.com: ns53.domaincontrol.com and ns54.domaincontrol.com.

securehhc.com shares its NS records with other domains, for example top10koreanmask.com, dlgsystems.com, zufriedenheitsmessung.com and two others.

ns53.domaincontrol.com and ns54.domaincontrol.com both carry two IP addresses. The A records for ns53.domaincontrol.com are 97.74.106.27 and 2603:5:21a2::1b; the A records for ns54.domaincontrol.com are 173.201.74.27 and 2603:5:22a2::1b.

Mail Servers

Five mail servers handle securehhc.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

There is at least a partial MX overlap between securehhc.com and other domains, including ns500671.ns500731.ns500671.ns500731.ns500742.ns500705.ns500671.ns500678.ns500688.ns500666.ns500666.ns500131.lustychickser.com, ns500698.ns500759.ns500698.ns500758.ns500735.ns500708.ns500708.ns500698.ns500652.ns500619.ns500619.ns500652.ns500619.ns500652.tracksymphony.com, metadigi.com.tw and two others.

These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Host names that have two IP addresses:

aspmx.l.google.com resolves to two addresses: 142.250.31.26 and 2607:f8b0:4004:c1b::1b.

alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.

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

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

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