inmap.co.nz checked at 2025-02-25T16:57:33.488Z 547ms 67/68/68 99% R:13
DNS.NINJA - inmap.co.nz
Search for IP or hostnames
inmap.co.nz
MX | in1-smtp.messagingengine.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 | in2-smtp.messagingengine.com | ||||||
A | 202.12.124.216 AS5716 | ||||||
PTR | stl-mx-01.messagingengine.com | ||||||
A | 202.12.124.217 AS5716 | ||||||
PTR | stl-mx-02.messagingengine.com |
co.nz
NS | ns1.dns.net.nz | ||||||
NS | ns2.dns.net.nz | ||||||
NS | ns3.dns.net.nz | ||||||
NS | ns4.dns.net.nz | ||||||
NS | ns5.dns.net.nz | ||||||
NS | ns6.dns.net.nz | ||||||
NS | ns7.dns.net.nz |
AI analysis
Two mail servers, in1-smtp.messagingengine.com and in2-smtp.messagingengine.com, manage inmap.co.nz.
Just like other domains such as animesuki.com, 1k2.nl, plokodelika.com, mail.techthisout.be, and schroer.ca, inmap.co.nz also has the same mail server setup.
Some mail servers are at least partially shared between inmap.co.nz and other domains such as james-nock.co.uk.
in1-smtp.messagingengine.com is associated with 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. Whereas in2-smtp.messagingengine.com is linked to two IP numbers: 202.12.124.216 and 202.12.124.217.
dbq