`medrecordsrequest.com`

DNSSEC	⚠️ Not signed
NS	`ns-cloud-a1.googledomains.com` ⭐
		A	2001:4860:4802:32::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a1.googledomains.com`
		A	216.239.32.106^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-a1.googledomains.com`
NS	`ns-cloud-a2.googledomains.com`
		A	2001:4860:4802:34::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a2.googledomains.com`
		A	216.239.34.106^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-a2.googledomains.com`
NS	`ns-cloud-a3.googledomains.com`
		A	2001:4860:4802:36::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a3.googledomains.com`
		A	216.239.36.106^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-a3.googledomains.com`
NS	`ns-cloud-a4.googledomains.com`
		A	2001:4860:4802:38::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a4.googledomains.com`
		A	216.239.38.106^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-a4.googledomains.com`
MX	`aspmx.l.google.com` ⭐
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:4013:c1e::1b^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqzs-in-f27.1e100.net`
		A	192.178.213.27^{🇺🇸 Google192.178.213.0/24}
			PTR	`yugrqzs-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`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c00::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f27.1e100.net`
			PTR	`ws-in-x1b.1e100.net`
		A	173.194.76.27^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f27.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
SOA	`ns-cloud-a1.googledomains.com`cloud-dns-hostmaster@google.com serial=13

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

Subdomains

admin.medrecordsrequest.com

Same first word

medrecordsrequest.com

DNS History

9 records (9 active, 0 former)

●NSns-cloud-a1.googledomains.com2026-03-25 → 2026-04-24 · 2 obs

● 2026-03-25 07:04:46
● 2026-04-24 20:59:40

●NSns-cloud-a2.googledomains.com2026-03-25 → 2026-04-24 · 2 obs

● 2026-03-25 07:04:46
● 2026-04-24 20:59:40

●NSns-cloud-a3.googledomains.com2026-03-25 → 2026-04-24 · 2 obs

● 2026-03-25 07:04:46
● 2026-04-24 20:59:40

●NSns-cloud-a4.googledomains.com2026-03-25 → 2026-04-24 · 2 obs

● 2026-03-25 07:04:46
● 2026-04-24 20:59:40

●MXalt1.aspmx.l.google.com2026-03-25 → 2026-04-24 · 2 obs

● 2026-03-25 07:04:46
● 2026-04-24 20:59:40

●MXalt2.aspmx.l.google.com2026-03-25 → 2026-04-24 · 2 obs

● 2026-03-25 07:04:46
● 2026-04-24 20:59:40

●MXalt3.aspmx.l.google.com2026-03-25 → 2026-04-24 · 2 obs

● 2026-03-25 07:04:46
● 2026-04-24 20:59:40

●MXalt4.aspmx.l.google.com2026-03-25 → 2026-04-24 · 2 obs

● 2026-03-25 07:04:46
● 2026-04-24 20:59:40

●MXaspmx.l.google.com2026-03-25 → 2026-04-24 · 2 obs

● 2026-03-25 07:04:46
● 2026-04-24 20:59:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
medrecordsrequest.com	ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com	8 records

✅ Authoritative Response

Server:216.239.34.106

NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 393ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-cloud-a4.googledomains.com, ns-cloud-a2.googledomains.com...`
MX	5	`alt3.aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
SOA	1	`ns-cloud-a1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)

Analysis

Hierarchy

The parent of admin.medrecordsrequest.com is medrecordsrequest.com.

Name Servers

medrecordsrequest.com is delegated to four name servers: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.

medrecordsrequest.com at least partially shares name servers with other domains, for instance kickoffmusic.com, jessicanutrition.com, lepalmierrouge.com, naturtonmeister.com and healthcareresourcemanagement.com.

Host names with two IP numbers: ns-cloud-a1.googledomains.com points to 2001:4860:4802:32::6a and 216.239.32.106; ns-cloud-a2.googledomains.com points to 2001:4860:4802:34::6a and 216.239.34.106; ns-cloud-a3.googledomains.com points to 2001:4860:4802:36::6a and 216.239.36.106; ns-cloud-a4.googledomains.com points to 2001:4860:4802:38::6a and 216.239.38.106.

Mail Servers

Five mail servers handle medrecordsrequest.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.

medrecordsrequest.com shares at least partially some mail servers with other domains, including ploteye.com, oculux.net, webactiv.ro, josalo.com and dralmonte.com.