`mediplanner.mx`

DNSSEC	⚠️ Not signed
A	3.82.113.185^{🇺🇸 Amazon3.80.0.0/12 EC2 IAD prefix}
		PTR	`ec2-3-82-113-185.compute-1.amazonaws.com`
NS	`ns-415.awsdns-51.com` ⭐
		A	2600:9000:5301:9f00::1^{🇺🇸 Amazon2600:9000:5301::/48 - CloudFront}
			PTR	`ns-415.awsdns-51.com`
		A	205.251.193.159^{🇺🇸 Amazon205.251.193.0/24 prefix}
			PTR	`ns-415.awsdns-51.com`
NS	`ns-1324.awsdns-37.org`
		A	2600:9000:5305:2c00::1^{🇺🇸 Amazon2600:9000:5305::/48 - CloudFront}
			PTR	`ns-1324.awsdns-37.org`
		A	205.251.197.44^{🇺🇸 Amazon205.251.197.0/24 prefix}
			PTR	`ns-1324.awsdns-37.org`
NS	`ns-1736.awsdns-25.co.uk`
		A	2600:9000:5306:c800::1^{🇺🇸 Amazon2600:9000:5306::/48 - CloudFront}
			PTR	`ns-1736.awsdns-25.co.uk`
		A	205.251.198.200^{🇺🇸 Amazon205.251.198.0/24 prefix}
			PTR	`ns-1736.awsdns-25.co.uk`
NS	`ns-552.awsdns-05.net`
		A	2600:9000:5302:2800::1^{🇺🇸 Amazon2600:9000:5302::/48 - CloudFront}
			PTR	`ns-552.awsdns-05.net`
		A	205.251.194.40^{🇺🇸 Amazon205.251.194.0/24 prefix}
			PTR	`ns-552.awsdns-05.net`
SOA	`ns-415.awsdns-51.com`awsdns-hostmaster@amazon.com serial=1

`mx`

	DNSSEC	🔒 Signed (DS record present)
	NS	`m.mx-ns.mx` ⭐
	NS	`c.mx-ns.mx`
	NS	`e.mx-ns.mx`
	NS	`i.mx-ns.mx`
	NS	`o.mx-ns.mx`
	NS	`x.mx-ns.mx`
	TXT	`v=spf1 -all`
	SOA	`m.mx-ns.mx`hostmaster@nic.mx serial=1778623261

Subdomains

admin-dev.mediplanner.mx

Same first word

mediplanner.mx

Similar names

redmapleinn.com

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	m.mx-ns.mx, x.mx-ns.mx, e.mx-ns.mx, c.mx-ns.mx...	-
mediplanner.mx	ns-415.awsdns-51.com, ns-1736.awsdns-25.co.uk, ns-1324.awsdns-37.org, ns-552.awsdns-05.net	-

✅ Authoritative Response

Server:205.251.194.40

NS records: ns-415.awsdns-51.com, ns-1736.awsdns-25.co.uk, ns-1324.awsdns-37.org, ns-552.awsdns-05.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mediplanner.mx (unsigned zone)

⏱️ Timing

Total: 347ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.82.113.185`
NS	4	`ns-1324.awsdns-37.org, ns-1736.awsdns-25.co.uk...`
SOA	1	`ns-415.awsdns-51.com awsdns-hostmaster.a`

Analysis

Hierarchy

The parent of admin-dev.mediplanner.mx is mediplanner.mx.

IP Addresses

mediplanner.mx points to a single IP number: 3.82.113.185.

Name Servers

mediplanner.mx is delegated to four name servers: ns-415.awsdns-51.com, ns-552.awsdns-05.net, ns-1324.awsdns-37.org and ns-1736.awsdns-25.co.uk.

mediplanner.mx shares name servers with other domains at least partially, for instance fanshield.insure, pubassets.com, monstertruckswashingtondc.com, d2a6omiizetjx1.cloudfront.net and d1r37ipvw8xhhm.cloudfront.net.

Host names with two IP numbers:

ns-415.awsdns-51.com resolves to 2600:9000:5301:9f00::1 and 205.251.193.159.

ns-552.awsdns-05.net resolves to 2600:9000:5302:2800::1 and 205.251.194.40.

ns-1324.awsdns-37.org resolves to 2600:9000:5305:2c00::1 and 205.251.197.44.

ns-1736.awsdns-25.co.uk resolves to 2600:9000:5306:c800::1 and 205.251.198.200.

mediplanner.mx - robtex.com

mediplanner.mx

mx