`doctorfrontera.com`

DNSSEC	⚠️ Not signed
A	54.184.192.203^{🇺🇸 Amazon54.184.0.0/15 EC2 PDX prefix}
		PTR	`ec2-54-184-192-203.us-west-2.compute.amazonaws.com`
NS	`ns301.cloud-mx-ns.net` ⭐
		A	72.249.55.100^{🇺🇸 TierPoint72.249.48.0/20 LLC}
			PTR	`ns301.cloud-mx-ns.net`
NS	`ns302.cloud-mx-ns.net`
		A	65.99.205.178^{🇺🇸 TierPoint65.99.192.0/18 LLC}
			PTR	`ns302.cloud-mx-ns.net`
NS	`ns303.cloud-mx-ns.net`
		A	65.99.252.139^{🇺🇸 TierPoint65.99.192.0/18 LLC}
			PTR	`ns303.cloud-mx-ns.net`
NS	`ns304.cloud-mx-ns.net`
		A	65.99.225.199^{🇺🇸 TierPoint65.99.192.0/18 LLC}
			PTR	`ns304.cloud-mx-ns.net`
NS	`ns305.cloud-mx-ns.net` ⚠️ Not in parent delegation
		A	66.240.233.158^{🇺🇸 AS1043966.240.192.0/18}
			PTR	`ns305.cloud-mx-ns.net`
MX	`doctorfrontera-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc3a::^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-qr0p297cu00300.inbound.protection.outlook.com`
		A	2a01:111:f403:cc3a::1^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-qr0p297cu00401.inbound.protection.outlook.com`
		A	2a01:111:f403:cc3a::2^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-qr1p297cu00202.inbound.protection.outlook.com`
		A	2a01:111:f403:cc3a::3^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-qr2p297cu00303.inbound.protection.outlook.com`
		A	52.101.232.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-qr0p297cu00300.inbound.protection.outlook.com`
		A	52.101.232.1^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-qr0p297cu00401.inbound.protection.outlook.com`
		A	52.101.232.2^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-qr1p297cu00202.inbound.protection.outlook.com`
		A	52.101.232.3^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-qr2p297cu00303.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns301.cloud-mx-ns.net`root@ns301.cloud-mx-ns.net 2026-05-07 #3

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

Same first word

doctorfrontera.com

DNS History

7 records (7 active, 0 former)

●NSns301.cloud-mx-ns.net2026-06-30 → 2026-07-31 · 2 obs

● 2026-06-30 02:36:26
● 2026-07-31 12:02:12

●NSns302.cloud-mx-ns.net2026-06-30 → 2026-07-31 · 2 obs

● 2026-06-30 02:36:26
● 2026-07-31 12:02:12

●NSns303.cloud-mx-ns.net2026-06-30 → 2026-07-31 · 2 obs

● 2026-06-30 02:36:26
● 2026-07-31 12:02:12

●NSns304.cloud-mx-ns.net2026-06-30 → 2026-07-31 · 2 obs

● 2026-06-30 02:36:26
● 2026-07-31 12:02:12

●NSns305.cloud-mx-ns.net2026-06-30 → 2026-07-31 · 2 obs

● 2026-06-30 02:36:26
● 2026-07-31 12:02:12

●MXdoctorfrontera-com.mail.protection.outlook.com2026-06-30 → 2026-07-31 · 2 obs

● 2026-06-30 02:36:26
● 2026-07-31 12:02:12

●A54.184.192.2032026-06-30 → 2026-07-31 · 2 obs

● 2026-06-30 02:36:26
● 2026-07-31 12:02:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	f.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, m.gtld-servers.net...	-
doctorfrontera.com	ns301.cloud-mx-ns.net, ns302.cloud-mx-ns.net, ns303.cloud-mx-ns.net, ns304.cloud-mx-ns.net	-

✅ Authoritative Response

Server:65.99.225.199

NS records: ns301.cloud-mx-ns.net, ns302.cloud-mx-ns.net, ns303.cloud-mx-ns.net, ns304.cloud-mx-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for doctorfrontera.com (unsigned zone)

⏱️ Timing

Total: 442ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.184.192.203`
NS	5	`ns302.cloud-mx-ns.net, ns305.cloud-mx-ns.net...`
MX	1	`doctorfrontera-com.mail.protection.outlo`
TXT	1	`v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns301.cloud-mx-ns.net root.ns304.cloud-m`

Analysis

IP Addresses

doctorfrontera.com resolves to just one IP address, 54.184.192.203.

Other host names share IP numbers with doctorfrontera.com; dgregenerative.com is one such example.

Name Servers

doctorfrontera.com delegates to five name servers: ns301.cloud-mx-ns.net, ns302.cloud-mx-ns.net, ns303.cloud-mx-ns.net and two others.

At least some of doctorfrontera.com's name servers are shared with other domains, for example nupiell.mx, sbetech.com, mascomprobantes.com and two more.

The name servers ns304.cloud-mx-ns.net, ns305.cloud-mx-ns.net, ns1.cprapid.com and two others are commonly seen in use alongside these name servers.

Host names that point to one IP address:

ns301.cloud-mx-ns.net points to the IP address 72.249.55.100.

ns302.cloud-mx-ns.net points to the IP address 65.99.205.178.

ns303.cloud-mx-ns.net points to the IP address 65.99.252.139.

ns304.cloud-mx-ns.net points to the IP address 65.99.225.199.

ns305.cloud-mx-ns.net points to the IP address 66.240.233.158.