DNSWHOIS.INFO - localization.me

Search for IP or hostnames:

localization.me checked at 2025-09-07T03:06:20.365Z 197ms 232/232/232 100% R:11

`localization.me`

NS	`ns27.domaincontrol.com`
		A	2603:5:2171::e ^{🇺🇸 GODADDY-DNS}
			PTR	`ns27.domaincontrol.com`
		A	97.74.103.14^{🇺🇸 GODADDY-DNS}
			PTR	`ns27.domaincontrol.com`
NS	`ns28.domaincontrol.com`
		A	2603:5:2271::e ^{🇺🇸 GODADDY-DNS}
			PTR	`ns28.domaincontrol.com`
		A	173.201.71.14^{🇺🇸 GODADDY-DNS}
			PTR	`ns28.domaincontrol.com`
MX	`mx-1.pobox.com`
		A	103.168.172.216^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-01.messagingengine.com`
		A	103.168.172.217^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-02.messagingengine.com`
		A	103.168.172.218^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-03.messagingengine.com`
		A	103.168.172.219^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-04.messagingengine.com`
		A	103.168.172.220^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-05.messagingengine.com`
		A	103.168.172.221^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-06.messagingengine.com`
		A	103.168.172.222^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-07.messagingengine.com`
		A	103.168.172.223^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-08.messagingengine.com`
MX	`mx-2.pobox.com`
		A	103.168.172.216^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-01.messagingengine.com`
		A	103.168.172.217^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-02.messagingengine.com`
		A	103.168.172.218^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-03.messagingengine.com`
		A	103.168.172.219^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-04.messagingengine.com`
		A	103.168.172.220^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-05.messagingengine.com`
		A	103.168.172.221^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-06.messagingengine.com`
		A	103.168.172.222^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-07.messagingengine.com`
		A	103.168.172.223^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-08.messagingengine.com`
MX	`mx-3.pobox.com`
		A	103.168.172.216^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-01.messagingengine.com`
		A	103.168.172.217^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-02.messagingengine.com`
		A	103.168.172.218^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-03.messagingengine.com`
		A	103.168.172.219^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-04.messagingengine.com`
		A	103.168.172.220^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-05.messagingengine.com`
		A	103.168.172.221^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-06.messagingengine.com`
		A	103.168.172.222^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-07.messagingengine.com`
		A	103.168.172.223^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-08.messagingengine.com`
MX	`mx-4.pobox.com`
		A	103.168.172.216^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-01.messagingengine.com`
		A	103.168.172.217^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-02.messagingengine.com`
		A	103.168.172.218^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-03.messagingengine.com`
		A	103.168.172.219^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-04.messagingengine.com`
		A	103.168.172.220^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-05.messagingengine.com`
		A	103.168.172.221^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-06.messagingengine.com`
		A	103.168.172.222^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-07.messagingengine.com`
		A	103.168.172.223^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-08.messagingengine.com`
MX	`mx-5.pobox.com`
		A	103.168.172.216^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-01.messagingengine.com`
		A	103.168.172.217^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-02.messagingengine.com`
		A	103.168.172.218^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-03.messagingengine.com`
		A	103.168.172.219^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-04.messagingengine.com`
		A	103.168.172.220^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-05.messagingengine.com`
		A	103.168.172.221^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-06.messagingengine.com`
		A	103.168.172.222^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-07.messagingengine.com`
		A	103.168.172.223^{🇺🇸 Cloudflare London}
			PTR	`phl-mx-08.messagingengine.com`
A	65.39.205.57^{🇨🇦 SQUARESPACE}

`me`

	NS	`a0.nic.me`
	NS	`a2.nic.me`
	NS	`b0.nic.me`
	NS	`b2.nic.me`
	NS	`c0.nic.me`

Starts with same word
`localization.it`
`localization.co.za`
`localization.delivery`
`localization.cn`
`localization.de`
`localization.ru`
`localization.co`
`localization.me`
`localization.engineering`
`localization.com`
`localization.us`
`localization.ee`
`localization.co.in`
`localization.agency`

Starts similarily
`localization.agency`
`localization.it`
`localization.co.za`
`localization.delivery`
`localization.cn`
`localization.de`
`localization.ru`
`localization.co`
`localization.me`
`localization.engineering`
`localization.com`
`localization.us`
`localization.ee`
`localization.co.in`

AI analysis

localization.me is associated with a single IP address: 65.39.205.57.

IP numbers are shared between localization.me and other host names such as kiro.ee, zoneedit.com.alvanmil.com, patriciademers.com, toddmiltenberger.com, and ebmarine.net.

Two name servers, ns27.domaincontrol.com and ns28.domaincontrol.com, are delegated to localization.me.

The name server setup for localization.me is shared with several other domains such as arisesom.com, verpackungsmonitor.de, eschilder.com, raftseat.com, and password-protect-video.com.

ns27.domaincontrol.com and ns28.domaincontrol.com each point to two IP numbers: 2603:5:2171::e, 97.74.103.14 and 2603:5:2271::e, 173.201.71.14 respectively.

Five mail servers, mx-1.pobox.com, mx-2.pobox.com, mx-3.pobox.com, mx-4.pobox.com, and mx-5.pobox.com, are responsible for handling localization.me.

Some mail servers are at least partially shared between localization.me and other domains, such as cosurvey.org, adventuresinrenaming.net, clients-prod.fr, hazeltreecourt.com, and archer.cx.

mx-1.pobox.com, mx-2.pobox.com, mx-3.pobox.com, mx-4.pobox.com, and mx-5.pobox.com all point to the same eight IP numbers: 103.168.172.216, 103.168.172.217, 103.168.172.218, 103.168.172.219, 103.168.172.220, 103.168.172.221, 103.168.172.222, and 103.168.172.223.

dbq