`fedexairman.com.mx`

DNSSEC	⚠️ Not signed
A	200.57.135.106^{🇲🇽 AS19373200.57.128.0/20 LACNIC generated route for Triara.com S.A. de C.V.}
		PTR	`dns2.infonetmx.com`
NS	`ns47.domaincontrol.com` ⭐
		A	2603:5:2172::18^{🇺🇸 GODADDY-DNS2603:5:2170::/44}
			PTR	`ns47.domaincontrol.com`
		A	97.74.103.24^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns47.domaincontrol.com`
NS	`ns48.domaincontrol.com`
		A	2603:5:2272::18^{🇺🇸 GODADDY-DNS2603:5:2270::/44}
			PTR	`ns48.domaincontrol.com`
		A	173.201.71.24^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns48.domaincontrol.com`
MX	`fedexairman-com-mx.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c922::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr05cu00501.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm6pr03cu00401.inbound.protection.outlook.com`
		A	2a01:111:f403:f804::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr05cu00301.inbound.protection.outlook.com`
		A	2a01:111:f403:f804::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-co1pr03cu00403.inbound.protection.outlook.com`
		A	52.101.9.11^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr04cu00103.inbound.protection.outlook.com`
		A	52.101.11.15^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sa9pr02cu00207.inbound.protection.outlook.com`
		A	52.101.41.3^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj2pr05cu00103.inbound.protection.outlook.com`
		A	52.101.194.12^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch0pr04cu00504.inbound.protection.outlook.com`
TXT	`NETORGFT12381916.onmicrosoft.com`
TXT	`v=spf1 include:secureserver.net -all`
SOA	`ns47.domaincontrol.com`dns@jomax.net 2022-12-30 #1

`com.mx`

	DNSSEC	⚠️ Not signed
	NS	`m.mx-ns.mx` ⭐ ⚠️ Not in parent delegation
	NS	`c.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`e.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`i.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`o.mx-ns.mx` ⚠️ Not in parent delegation
	NS	`x.mx-ns.mx` ⚠️ Not in parent delegation
	TXT	`v=spf1 -all`
	SOA	`m.mx-ns.mx`hostmaster@nic.mx serial=1784413116

WOT: NOT_SAFE (44/100)

Same first word

fedexairman.com.mx

DNS History

14 records (4 active, 10 former)

○NSns1.no-ip.com2015-08-22 → 2016-06-24 · 4 obs

● 2015-08-22 15:58:54
● 2016-06-24 11:00:32
○ 2017-02-18 13:40:34
○ 2026-07-18 22:23:14

○NSns2.no-ip.com2015-08-22 → 2016-06-24 · 4 obs

● 2015-08-22 15:58:54
● 2016-06-24 11:00:32
○ 2017-02-18 13:40:34
○ 2026-07-18 22:23:14

○NSns3.no-ip.com2015-08-22 → 2016-06-24 · 4 obs

● 2015-08-22 15:58:54
● 2016-06-24 11:00:32
○ 2017-02-18 13:40:34
○ 2026-07-18 22:23:14

○NSns4.no-ip.com2015-08-22 → 2016-06-24 · 4 obs

● 2015-08-22 15:58:54
● 2016-06-24 11:00:32
○ 2017-02-18 13:40:34
○ 2026-07-18 22:23:14

●NSns47.domaincontrol.com2017-02-18 → 2026-07-18 · 3 obs

○ 2016-06-24 11:00:32
● 2017-02-18 13:40:34
● 2026-07-18 22:23:14

●NSns48.domaincontrol.com2017-02-18 → 2026-07-18 · 3 obs

○ 2016-06-24 11:00:32
● 2017-02-18 13:40:34
● 2026-07-18 22:23:14

○NSns5.no-ip.com2015-08-22 → 2016-06-24 · 4 obs

● 2015-08-22 15:58:54
● 2016-06-24 11:00:32
○ 2017-02-18 13:40:34
○ 2026-07-18 22:23:14

●MXfedexairman-com-mx.mail.protection.outlook.com2026-06-28 → 2026-07-18 · 3 obs

○ 2020-02-18 02:45:50
● 2026-06-28 15:11:26
● 2026-07-18 22:23:14

○MXmailstore1.secureserver.net2017-02-18 → 2020-02-18 · 5 obs

○ 2016-06-24 11:00:32
● 2017-02-18 13:40:34
● 2020-02-18 02:45:50
○ 2026-06-28 15:11:26
○ 2026-07-18 22:23:14

○MXmx.noip.com2015-08-22 → 2016-06-24 · 4 obs

● 2015-08-22 15:58:54
● 2016-06-24 11:00:32
○ 2017-02-18 13:40:34
○ 2026-07-18 22:23:14

○MXsmtp.secureserver.net2017-02-18 → 2020-02-18 · 5 obs

○ 2016-06-24 11:00:32
● 2017-02-18 13:40:34
● 2020-02-18 02:45:50
○ 2026-06-28 15:11:26
○ 2026-07-18 22:23:14

●A200.57.135.1062026-06-28 → 2026-07-18 · 3 obs

○ 2020-02-18 02:45:50
● 2026-06-28 15:11:26
● 2026-07-18 22:23:14

○A200.57.135.982020-02-18 → 2020-02-18 · 4 obs

○ 2017-02-18 13:40:34
● 2020-02-18 02:45:50
○ 2026-06-28 15:11:26
○ 2026-07-18 22:23:14

○A200.57.142.682015-08-22 → 2017-02-18 · 4 obs

● 2015-08-22 15:58:54
● 2017-02-18 13:40:34
○ 2020-02-18 02:45:50
○ 2026-07-18 22:23:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
mx	o.mx-ns.mx, i.mx-ns.mx, e.mx-ns.mx, c.mx-ns.mx...	-
fedexairman.com.mx	ns47.domaincontrol.com, ns48.domaincontrol.com	-

✅ Authoritative Response

Server:173.201.71.24

NS records: ns47.domaincontrol.com, ns48.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fedexairman.com.mx (unsigned zone)

⏱️ Timing

Total: 529ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`200.57.135.106`
NS	2	`ns47.domaincontrol.com, ns48.domaincontrol.com`
MX	1	`fedexairman-com-mx.mail.protection.outlo`
TXT	2	`NETORGFT12381916.onmicrosoft.com, v=spf1 include:secureserver.net -all`
SOA	1	`ns47.domaincontrol.com dns.jomax.net`

Analysis

IP Addresses

fedexairman.com.mx directs to one IP number, which is 200.57.135.106.

Name Servers

The NS records for fedexairman.com.mx delegate to ns47.domaincontrol.com and ns48.domaincontrol.com.

fedexairman.com.mx has the same name server delegation as a number of other domains, such as 10xmypay.com, messnyc.com, costaricabitcoin.com and two more.

fedexairman.com.mx shares at least some of its name servers with other domains, such as azizla.com and secureclick.net.

ns47.domaincontrol.com resolves to 97.74.103.24 and 2603:5:2172::18. Likewise, ns48.domaincontrol.com resolves to 173.201.71.24 and 2603:5:2272::18 — two IP addresses apiece.

Mail Servers

fedexairman.com.mx routes its mail through a single mail server, fedexairman-com-mx.mail.protection.outlook.com.

fedexairman-com-mx.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.9.11, 52.101.11.15 and 52.101.41.3, along with 5 other.

fedexairman.com.mx - robtex.com