ip02.net - dns.ninja

`ip02.net`

DNSSEC	⚠️ Not signed
A	38.102.43.132^{🇺🇸 COGENT38.102.40.0/22}
A	64.84.6.72^{🇺🇸 RAGINGWIRE64.84.6.0/24 iPost}
A	204.94.81.43^{🇺🇸 RAGINGWIRE204.94.80.0/20 RagingWire Data Centers, Inc.}
NS	`dns01.ipost.com` ⭐
		A	64.84.6.50^{🇺🇸 RAGINGWIRE64.84.6.0/24 iPost}
			PTR	`dns01.ipost.com`
NS	`dns01.smf.ipost.com`
		A	204.94.81.2^{🇺🇸 RAGINGWIRE204.94.80.0/20 RagingWire Data Centers, Inc.}
			PTR	`dns01.smf.ipost.com`
		A	204.94.81.5^{🇺🇸 RAGINGWIRE204.94.80.0/20 RagingWire Data Centers, Inc.}
			PTR	`dns01.smf.ipost.com`
MX	`mx2.ipost.com` ⭐
		A	64.84.5.19^{🇺🇸 RAGINGWIRE64.84.5.0/24 iPost}
			PTR	`mx2.ipost.com`
		A	64.84.6.42^{🇺🇸 RAGINGWIRE64.84.6.0/24 iPost}
			PTR	`mx2.ipost.com`
MX	`mx4.ipost.com` ⭐
		A	64.84.6.52^{🇺🇸 RAGINGWIRE64.84.6.0/24 iPost}
			PTR	`mx4.ipost.com`
MX	`mx6.ipost.com` ⭐
		A	64.84.6.48^{🇺🇸 RAGINGWIRE64.84.6.0/24 iPost}
			PTR	`mx6.ipost.com`
TXT	`google-site-verification=V6vIw_gTQf1f-wNCxFu1s1RHWTGs5Aep-MVpDilRmCk`
TXT	`v=spf1 ip4:64.84.5.0/27 ip4:64.84.6.0/24 ip4:204.94.81.0/24 ip4:64.84.38.0/24...`
SOA	`dns01.ipost.com`hostmaster@zanshin.com 2026-06-10 #1

`net`

	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=1783857367

Same first word

ip02.org

ip02.com

ip02.de

ip02.net

Similar names

20ip.com

02ip.ru

ip20.de

ip20.nl

02pi.com

ip20.ch

ip20.org

i2p0.com

ip20.eu

ip20.com

ip20.ir

pi20.com

02ip.com

pi02.net

pi02.com

ip20.cn

20pi.com

DNS History

12 records (8 active, 4 former)

●NSdns01.ipost.com2015-06-17 → 2026-07-12 · 2 obs

● 2015-06-17 08:30:10
● 2026-07-12 12:21:52

●NSdns01.smf.ipost.com2015-06-17 → 2026-07-12 · 2 obs

● 2015-06-17 08:30:10
● 2026-07-12 12:21:52

●MXmx2.ipost.com2015-06-17 → 2026-07-12 · 2 obs

● 2015-06-17 08:30:10
● 2026-07-12 12:21:52

○MXmx3.ipost.com2015-06-17 → 2016-07-23 · 4 obs

● 2015-06-17 08:30:10
● 2016-07-23 18:58:54
○ 2026-03-22 19:15:36
○ 2026-07-12 12:21:52

●MXmx4.ipost.com2015-06-17 → 2026-07-12 · 2 obs

● 2015-06-17 08:30:10
● 2026-07-12 12:21:52

○MXmx5.ipost.com2015-06-17 → 2016-07-23 · 4 obs

● 2015-06-17 08:30:10
● 2016-07-23 18:58:54
○ 2026-03-22 19:15:36
○ 2026-07-12 12:21:52

●MXmx6.ipost.com2026-03-22 → 2026-07-12 · 3 obs

○ 2016-07-23 18:58:54
● 2026-03-22 19:15:36
● 2026-07-12 12:21:52

○A204.94.81.142015-06-17 → 2016-07-23 · 4 obs

● 2015-06-17 08:30:10
● 2016-07-23 18:58:54
○ 2026-03-22 19:15:36
○ 2026-07-12 12:21:52

●A204.94.81.432026-03-22 → 2026-07-12 · 3 obs

○ 2016-07-23 18:58:54
● 2026-03-22 19:15:36
● 2026-07-12 12:21:52

●A38.102.43.1322026-03-22 → 2026-07-12 · 3 obs

○ 2016-07-23 18:58:54
● 2026-03-22 19:15:36
● 2026-07-12 12:21:52

○A64.84.6.402015-06-17 → 2016-07-23 · 4 obs

● 2015-06-17 08:30:10
● 2016-07-23 18:58:54
○ 2026-03-22 19:15:36
○ 2026-07-12 12:21:52

●A64.84.6.722026-03-22 → 2026-07-12 · 3 obs

○ 2016-07-23 18:58:54
● 2026-03-22 19:15:36
● 2026-07-12 12:21:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
ip02.net	dns01.ipost.com, dns01.smf.ipost.com	-

✅ Authoritative Response

Server:204.94.81.5

NS records: dns01.ipost.com, dns01.smf.ipost.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ip02.net (unsigned zone)

⏱️ Timing

Total: 1076ms | Queries: -

📄 Records

Type	Count	Sample Data
A	3	`64.84.6.72, 204.94.81.43...`
NS	2	`dns01.ipost.com, dns01.smf.ipost.com`
MX	3	`mx6.ipost.com (pri: 10), mx4.ipost.com (pri: 10)...`
TXT	2	`v=spf1 ip4:64.84.5.0/27 ip4:64.84.6.0/24, google-site-verification=V6vIw_gTQf1f-wN`
SOA	1	`dns01.ipost.com hostmaster.zanshin.com`

Analysis

IP Addresses

ip02.net resolves to three IP addresses: 38.102.43.132, 64.84.6.72 and 204.94.81.43.

Two other host names, along with ip04.com, www.ip08.com and ip03.com, also share IP numbers with ip02.net.

Name Servers

ip02.net is served by two delegated name servers, dns01.ipost.com and dns01.smf.ipost.com.

ip02.net shares its NS records with other domains, for example e.epiqnotice.com, glm.bbiinternational.com, e.emailksa.com and two others.

ip02.net shares at least some of its name servers with other domains, including escrip.com, m.sstack.com, email.sstack.com and two others.

Host names that have two IP addresses:

dns01.smf.ipost.com maps to two IP addresses — 204.94.81.2 and 204.94.81.5.

Host names that point to one IP address:

dns01.ipost.com points to the IP address 64.84.6.50.

Mail Servers

ip02.net is handled by three mail servers: mx2.ipost.com, mx4.ipost.com and mx6.ipost.com.

There is at least a partial MX overlap between ip02.net and other domains, including ip04.net, ip09.com, bluepaypci.com and two others.

These mail servers frequently appear alongside the mail servers mx3.ipost.com and mx5.ipost.com.

Host names that have two IP addresses:

mx2.ipost.com maps to two IP addresses — 64.84.5.19 and 64.84.6.42.

Host names that point to one IP address:

mx4.ipost.com points to the IP address 64.84.6.52.

mx6.ipost.com points to the IP address 64.84.6.48.