mapinfor.com - dns.ninja

`mapinfor.com`

DNSSEC	⚠️ Not signed
A	177.210.102.17^{🇧🇷 UNSPECIFIED160.0.0.0/3}
NS	`ns1.julydns.com` ⭐ ⚠️ Not in parent delegation
		A	162.159.48.223^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns1.onclouddns.com` ⚠️ Not in zone NS records
		A	162.159.27.251^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.julydns.com` ⚠️ Not in parent delegation
		A	162.159.48.223^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.onclouddns.com` ⚠️ Not in zone NS records
		A	162.159.27.251^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`ns1.julydns.com`master@jmdns.com serial=1784123967

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

Same first word

mapinfor.net

mapinfor.com

Similar names

DNS History

21 records (5 active, 16 former)

○NSns1.judns.com2026-02-15 → 2026-02-15 · 4 obs

○ 2017-07-08 15:21:24
● 2026-02-15 14:24:04
○ 2026-07-16 00:30:46
○ 2026-08-06 09:07:46

●NSns1.julydns.com2026-02-15 → 2026-08-06 · 3 obs

○ 2017-07-08 15:21:24
● 2026-02-15 14:24:04
● 2026-08-06 09:07:46

○NSns1.namebrightdns.com2015-07-08 → 2017-07-08 · 4 obs

● 2015-07-08 00:24:34
● 2017-07-08 15:21:24
○ 2026-02-15 14:24:04
○ 2026-08-06 09:07:46

●NSns1.onclouddns.com2026-07-16 → 2026-08-06 · 3 obs

○ 2026-02-15 14:24:04
● 2026-07-16 00:30:46
● 2026-08-06 09:07:46

○NSns2.judns.com2026-02-15 → 2026-02-15 · 4 obs

○ 2017-07-08 15:21:24
● 2026-02-15 14:24:04
○ 2026-07-16 00:30:46
○ 2026-08-06 09:07:46

●NSns2.julydns.com2026-02-15 → 2026-08-06 · 3 obs

○ 2017-07-08 15:21:24
● 2026-02-15 14:24:04
● 2026-08-06 09:07:46

○NSns2.namebrightdns.com2015-07-08 → 2017-07-08 · 4 obs

● 2015-07-08 00:24:34
● 2017-07-08 15:21:24
○ 2026-02-15 14:24:04
○ 2026-08-06 09:07:46

●NSns2.onclouddns.com2026-07-16 → 2026-08-06 · 3 obs

○ 2026-02-15 14:24:04
● 2026-07-16 00:30:46
● 2026-08-06 09:07:46

○MXanmail.namebrightmail.com2015-07-08 → 2015-07-08 · 3 obs

● 2015-07-08 00:24:34
○ 2015-11-13 09:43:24
○ 2026-08-06 09:07:46

○A107.23.95.2352015-07-08 → 2015-07-08 · 3 obs

● 2015-07-08 00:24:34
○ 2017-07-08 15:21:24
○ 2026-08-06 09:07:46

●A177.210.102.172026-07-16 → 2026-08-06 · 3 obs

○ 2026-02-15 14:24:04
● 2026-07-16 00:30:46
● 2026-08-06 09:07:46

○A38.239.106.2142026-02-15 → 2026-02-15 · 4 obs

○ 2017-07-08 15:21:24
● 2026-02-15 14:24:04
○ 2026-07-16 00:30:46
○ 2026-08-06 09:07:46

○A52.0.96.242016-02-09 → 2016-02-09 · 4 obs

○ 2015-11-13 09:43:24
● 2016-02-09 09:56:24
○ 2016-07-17 05:14:14
○ 2026-08-06 09:07:46

○A52.201.19.1702016-07-17 → 2016-07-17 · 4 obs

○ 2016-02-09 09:56:24
● 2016-07-17 05:14:14
○ 2017-07-08 15:21:24
○ 2026-08-06 09:07:46

○A52.202.238.1262016-07-17 → 2016-07-17 · 4 obs

○ 2016-02-09 09:56:24
● 2016-07-17 05:14:14
○ 2017-07-08 15:21:24
○ 2026-08-06 09:07:46

○A52.71.117.992016-02-09 → 2016-02-09 · 4 obs

○ 2015-11-13 09:43:24
● 2016-02-09 09:56:24
○ 2016-07-17 05:14:14
○ 2026-08-06 09:07:46

○A54.174.31.2542015-11-13 → 2015-11-13 · 4 obs

○ 2015-07-08 00:24:34
● 2015-11-13 09:43:24
○ 2016-02-09 09:56:24
○ 2026-08-06 09:07:46

○A54.208.74.2152015-11-13 → 2015-11-13 · 4 obs

○ 2015-07-08 00:24:34
● 2015-11-13 09:43:24
○ 2016-02-09 09:56:24
○ 2026-08-06 09:07:46

○A54.84.74.522015-07-08 → 2015-07-08 · 3 obs

● 2015-07-08 00:24:34
○ 2017-07-08 15:21:24
○ 2026-08-06 09:07:46

○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-07-08 → 2016-07-17 · 4 obs

● 2015-07-08 00:24:34
● 2016-07-17 05:14:14
○ 2017-07-08 15:21:24
○ 2026-08-06 09:07:46

○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-07-08 → 2026-02-16 · 5 obs

○ 2016-07-17 05:14:14
● 2017-07-08 15:21:24
● 2026-02-16 06:22:20
○ 2026-02-21 14:03:56
○ 2026-08-06 09:07:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
mapinfor.com	ns1.onclouddns.com, ns2.onclouddns.com	2 records

✅ Authoritative Response

Server:162.159.27.251

NS records: ns1.onclouddns.com, ns2.onclouddns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mapinfor.com (unsigned zone)

⏱️ Timing

Total: 250ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`177.210.102.17`
NS	2	`ns1.julydns.com, ns2.julydns.com`
SOA	1	`ns1.julydns.com master.jmdns.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.onclouddns.com, ns2.onclouddns.com)

Analysis

IP Addresses

mapinfor.com points to a single IP number: 177.210.102.17.

Additional host names — including slxifenche.net and kmocheng.com — share IP numbers with mapinfor.com.

Name Servers

mapinfor.com has four authoritative name servers: ns1.julydns.com, ns2.julydns.com, ns1.onclouddns.com and ns2.onclouddns.com.

mapinfor.com has at least partial name server overlap with other domains, such as zjhjzm.com, x3817.com, lfob.cn and two others.

It is common to see these name servers used together with name servers ns1.judns.com and ns2.judns.com.

ns1.julydns.com and ns2.julydns.com each resolve to 162.159.48.223, while ns1.onclouddns.com and ns2.onclouddns.com each resolve to 162.159.27.251.

ns1.julydns.com along with ns2.julydns.com each resolve to 162.159.48.223 IP addresses.

ns1.onclouddns.com along with ns2.onclouddns.com each resolve to 162.159.27.251 IP addresses.