regencyhcs.com - dns.ninja

`regencyhcs.com`

DNSSEC	⚠️ Not signed
A	198.202.211.1^{🇺🇸 CLOUDFLARESPECTRUM198.202.211.0/24 Webflow}
NS	`hadlee.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:2643^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`hadlee.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c243^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`hadlee.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2243^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`hadlee.ns.cloudflare.com`
		A	108.162.194.67^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`hadlee.ns.cloudflare.com`
		A	162.159.38.67^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`hadlee.ns.cloudflare.com`
		A	172.64.34.67^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`hadlee.ns.cloudflare.com`
NS	`jeremy.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bb4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jeremy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1b4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jeremy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21b4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jeremy.ns.cloudflare.com`
		A	108.162.193.180^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jeremy.ns.cloudflare.com`
		A	172.64.33.180^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jeremy.ns.cloudflare.com`
		A	173.245.59.180^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jeremy.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c09::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f26.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-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::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.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::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
TXT	`google-site-verification=C66Saz1GSShv8vv_vLU9zKf5wr5EEzU8TFE3WV2o0dI`
TXT	`v=spf1 include:_spf.google.com include:spf.de.exclaimer.net ip4:20.170.110.16...`
SOA	`hadlee.ns.cloudflare.com`dns@cloudflare.com serial=2405424986

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

Same first word

regencyhcs.com

DNS History

20 records (7 active, 13 former)

●NShadlee.ns.cloudflare.com2026-04-15 → 2026-07-24 · 3 obs

○ 2019-12-27 16:28:10
● 2026-04-15 04:40:22
● 2026-07-24 02:00:58

●NSjeremy.ns.cloudflare.com2026-04-15 → 2026-07-24 · 3 obs

○ 2019-12-27 16:28:10
● 2026-04-15 04:40:22
● 2026-07-24 02:00:58

○NSns-us.1and1-dns.com2015-05-31 → 2017-02-13 · 4 obs

● 2015-05-31 10:37:04
● 2017-02-13 07:10:20
○ 2019-12-27 16:28:10
○ 2026-07-24 02:00:58

○NSns-us.1and1-dns.de2015-05-31 → 2017-02-13 · 4 obs

● 2015-05-31 10:37:04
● 2017-02-13 07:10:20
○ 2019-12-27 16:28:10
○ 2026-07-24 02:00:58

○NSns-us.1and1-dns.org2015-05-31 → 2017-02-13 · 4 obs

● 2015-05-31 10:37:04
● 2017-02-13 07:10:20
○ 2019-12-27 16:28:10
○ 2026-07-24 02:00:58

○NSns-us.1and1-dns.us2015-05-31 → 2017-02-13 · 4 obs

● 2015-05-31 10:37:04
● 2017-02-13 07:10:20
○ 2019-12-27 16:28:10
○ 2026-07-24 02:00:58

○NSns1030.ui-dns.biz2019-12-27 → 2019-12-27 · 4 obs

○ 2017-02-13 07:10:20
● 2019-12-27 16:28:10
○ 2026-04-15 04:40:22
○ 2026-07-24 02:00:58

○NSns1030.ui-dns.com2019-12-27 → 2019-12-27 · 4 obs

○ 2017-02-13 07:10:20
● 2019-12-27 16:28:10
○ 2026-04-15 04:40:22
○ 2026-07-24 02:00:58

○NSns1030.ui-dns.de2019-12-27 → 2019-12-27 · 4 obs

○ 2017-02-13 07:10:20
● 2019-12-27 16:28:10
○ 2026-04-15 04:40:22
○ 2026-07-24 02:00:58

○NSns1030.ui-dns.org2019-12-27 → 2019-12-27 · 4 obs

○ 2017-02-13 07:10:20
● 2019-12-27 16:28:10
○ 2026-04-15 04:40:22
○ 2026-07-24 02:00:58

●MXalt1.aspmx.l.google.com2015-05-31 → 2026-07-24 · 2 obs

● 2015-05-31 10:37:04
● 2026-07-24 02:00:58

●MXalt2.aspmx.l.google.com2015-05-31 → 2026-07-24 · 2 obs

● 2015-05-31 10:37:04
● 2026-07-24 02:00:58

●MXalt3.aspmx.l.google.com2015-05-31 → 2026-07-24 · 2 obs

● 2015-05-31 10:37:04
● 2026-07-24 02:00:58

●MXaspmx.l.google.com2015-05-31 → 2026-07-24 · 2 obs

● 2015-05-31 10:37:04
● 2026-07-24 02:00:58

○A192.195.77.1962016-06-19 → 2017-02-13 · 5 obs

○ 2015-12-29 19:40:54
● 2016-06-19 02:01:36
● 2017-02-13 07:10:20
○ 2019-12-27 16:28:10
○ 2026-07-24 02:00:58

●A198.202.211.12026-04-15 → 2026-07-24 · 3 obs

○ 2019-12-27 16:28:10
● 2026-04-15 04:40:22
● 2026-07-24 02:00:58

○A198.251.65.1792015-05-31 → 2015-12-29 · 4 obs

● 2015-05-31 10:37:04
● 2015-12-29 19:40:54
○ 2016-06-19 02:01:36
○ 2026-07-24 02:00:58

○A2607:f1c0:1000:2011:5b69:bef3:1873:58142016-06-19 → 2017-02-13 · 5 obs

○ 2015-12-29 19:40:54
● 2016-06-19 02:01:36
● 2017-02-13 07:10:20
○ 2019-12-27 16:28:10
○ 2026-07-24 02:00:58

○A2607:f1c0:1000:2011:a710:c6d3:e86e:40062015-05-31 → 2015-12-29 · 4 obs

● 2015-05-31 10:37:04
● 2015-12-29 19:40:54
○ 2016-06-19 02:01:36
○ 2026-07-24 02:00:58

○A37.60.225.992019-12-27 → 2019-12-27 · 4 obs

○ 2017-02-13 07:10:20
● 2019-12-27 16:28:10
○ 2026-04-15 04:40:22
○ 2026-07-24 02:00:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net...	-
regencyhcs.com	jeremy.ns.cloudflare.com, hadlee.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.193.180

NS records: jeremy.ns.cloudflare.com, hadlee.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for regencyhcs.com (unsigned zone)

⏱️ Timing

Total: 238ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`198.202.211.1`
NS	2	`hadlee.ns.cloudflare.com, jeremy.ns.cloudflare.com`
MX	4	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`google-site-verification=C66Saz1GSShv8vv, v=spf1 include:_spf.google.com include:s`
SOA	1	`hadlee.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (jeremy.ns.cloudflare.com, jeremy.ns.cloudflare.com, jeremy.ns.cloudflare.com...)

Analysis

IP Addresses

regencyhcs.com resolves to one IP address: 198.202.211.1.

elumynt.com, greatamericantours.com, exigy.co.uk and two other host names share IP numbers with regencyhcs.com.

Name Servers

The NS records for regencyhcs.com delegate to hadlee.ns.cloudflare.com and jeremy.ns.cloudflare.com.

regencyhcs.com uses the same name servers as several other domains — among them trkksync.com, toto90.tech, 9ubet.club and two more.

There is at least partial name server overlap between regencyhcs.com and other domains — gestorimob.com.br, recepoglu.net, kadinjombangkab.org and two more among them.

These name servers frequently co-occur with the name servers shane.ns.cloudflare.com and achiel.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

hadlee.ns.cloudflare.com maps to 108.162.194.67, 162.159.38.67, 172.64.34.67 and 3 additional IP addresses.

jeremy.ns.cloudflare.com maps to 108.162.193.180, 172.64.33.180, 173.245.59.180 and 3 additional IP addresses.

Mail Servers

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

regencyhcs.com has at least partial mail server overlap with other domains such as securedata.com.br, sheelimpex.com, drispa.com and two more.

These mail servers commonly appear together with alt4.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com and two other mail servers.

All four hostnames — aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and alt3.aspmx.l.google.com — resolve to two IP numbers apiece: aspmx.l.google.com to 142.251.163.26 and 2607:f8b0:4004:c09::1a; 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::1b; alt3.aspmx.l.google.com to 192.178.223.26 and 2a00:1450:4009:c0f::1b.