`metlifeimplementation.com`

DNSSEC	⚠️ Not signed
NS	`ns2.metlife.com` ⭐
		A	216.163.240.251^{🇺🇸 AS203216.163.240.0/24}
			PTR	`ns2.metlife.com`
NS	`ns.metlife.com`
		A	216.163.249.248^{🇺🇸 AS203216.163.249.0/24}
			PTR	`ns.metlife.com`
			PTR	`ns.metlife.com.safeguard.net`
NS	`ns3.metlife.com`
		A	209.164.208.172^{🇺🇸 AS203209.164.208.0/24}
			PTR	`ns3.metlife.com`
MX	`mx1.hc1983-11.iphmx.com` ⭐
		A	68.232.157.126^{🇺🇸 CISCO-168.232.157.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	68.232.157.134^{🇺🇸 CISCO-168.232.157.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	68.232.157.141^{🇺🇸 CISCO-168.232.157.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	68.232.157.163^{🇺🇸 CISCO-168.232.157.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.33.11^{🇺🇸 CISCO-1139.138.33.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.33.12^{🇺🇸 CISCO-1139.138.33.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.33.13^{🇺🇸 CISCO-1139.138.33.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.33.15^{🇺🇸 CISCO-1139.138.33.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.33.23^{🇺🇸 CISCO-1139.138.33.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.33.24^{🇺🇸 CISCO-1139.138.33.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.56.184^{🇺🇸 CISCO-1139.138.56.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.56.187^{🇺🇸 CISCO-1139.138.56.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.56.188^{🇺🇸 CISCO-1139.138.56.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.56.189^{🇺🇸 CISCO-1139.138.56.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.56.198^{🇺🇸 CISCO-1139.138.56.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	139.138.56.199^{🇺🇸 CISCO-1139.138.56.0/24 170 West Tasman Drive San Jose CA 95134 United States}
		A	216.71.155.54^{🇺🇸 CISCO-1216.71.154.0/23 NAP5}
		A	216.71.155.56^{🇺🇸 CISCO-1216.71.154.0/23 NAP5}
		A	216.71.155.62^{🇺🇸 CISCO-1216.71.154.0/23 NAP5}
		A	216.71.155.64^{🇺🇸 CISCO-1216.71.154.0/23 NAP5}
TXT	`v=spf1 include:_spf.metlife.com -all`
SOA	`ns.metlife.com`hostmaster@metlife.com serial=37

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

Same first word

metlifeimplementation.com

DNS History

7 records (4 active, 3 former)

●NSns.metlife.com2016-12-16 → 2026-03-23 · 2 obs

● 2016-12-16 03:23:32
● 2026-03-23 23:26:00

●NSns2.metlife.com2016-12-16 → 2026-03-23 · 2 obs

● 2016-12-16 03:23:32
● 2026-03-23 23:26:00

●NSns3.metlife.com2016-12-16 → 2026-03-23 · 2 obs

● 2016-12-16 03:23:32
● 2026-03-23 23:26:00

○NSns4.metlife.com2016-12-16 → 2016-12-16 · 3 obs

● 2016-12-16 03:23:32
○ 2019-12-25 16:54:06
○ 2026-03-23 23:26:00

○MXms1.metlifecommercial.com2016-12-16 → 2019-12-25 · 4 obs

● 2016-12-16 03:23:32
● 2019-12-25 16:54:06
○ 2026-02-24 19:54:14
○ 2026-03-23 23:26:00

○MXms2.metlifecommercial.com2016-12-16 → 2019-12-25 · 4 obs

● 2016-12-16 03:23:32
● 2019-12-25 16:54:06
○ 2026-02-24 19:54:14
○ 2026-03-23 23:26:00

●MXmx1.hc1983-11.iphmx.com2026-02-24 → 2026-03-23 · 3 obs

○ 2019-12-25 16:54:06
● 2026-02-24 19:54:14
● 2026-03-23 23:26:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, j.gtld-servers.net, i.gtld-servers.net, e.gtld-servers.net...	-
metlifeimplementation.com	ns3.metlife.com, ns.metlife.com, ns2.metlife.com	3 records

✅ Authoritative Response

Server:209.164.208.172

NS records: ns3.metlife.com, ns.metlife.com, ns2.metlife.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for metlifeimplementation.com (unsigned zone)

⏱️ Timing

Total: 260ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	3	`ns2.metlife.com, ns3.metlife.com...`
MX	1	`mx1.hc1983-11.iphmx.com (pri: 100)`
TXT	1	`v=spf1 include:_spf.metlife.com -all`
SOA	1	`ns.metlife.com hostmaster.metlife.com`

📌 Glue Records Collected

Total: 3

Out-of-bailiwick: 3 (ns3.metlife.com, ns.metlife.com, ns2.metlife.com)

Analysis

Name Servers

metlifeimplementation.com is delegated to three name servers: ns2.metlife.com, ns3.metlife.com and ns.metlife.com.

metlifeimplementation.com at least partially shares name servers with other domains, for example 26.97.32.in-addr.arpa, metlifepetinsurance.com, metlifestock.com, metlifedevop.com and feelookup.com.

these name servers are commonly used with a1-254.akam.net, a13-67.akam.net, a2-64.akam.net, a24-65.akam.net, a4-66.akam.net and a7-67.akam.net.

Host names with a single IP address:

ns2.metlife.com resolves to 216.163.240.251.

ns3.metlife.com resolves to 209.164.208.172.

ns.metlife.com resolves to 216.163.249.248.

Mail Servers

The mx1.hc1983-11.iphmx.com mail server handles metlifeimplementation.com.

metlifeimplementation.com shares the same mail server setup as other domains, such as hrmetlife.com and metcommmail.com.

metlifeimplementation.com shares at least partially some mail servers with other domains, for instance logancirclepartners.com, metcommapp.com, metbatch.com, lpmservices-metlife.com and lcpim.com.

these mail servers are often used together with mx1.metlife.com, mx2.metlife.com and mx2.hc1983-11.iphmx.com.

Hostname mx1.hc1983-11.iphmx.com resolves to twenty IP numbers: 68.232.157.126, 68.232.157.134, 68.232.157.141, 68.232.157.163, 139.138.33.11, 139.138.33.12, 139.138.33.13, 139.138.33.15, 139.138.33.23, 139.138.33.24, 139.138.56.184, 139.138.56.187, 139.138.56.188, 139.138.56.189, 139.138.56.198, 139.138.56.199, 216.71.155.54, 216.71.155.56, 216.71.155.62 and 216.71.155.64.

metlifeimplementation.com - robtex.com