ip4.network - dns.ninja

ip4.network

DNSSEC⚠️ Not signed
NS0.011001000110111001110011.com ⭐
A2001:470:1f13:15f::8888πŸ‡ΊπŸ‡Έ HURRICANE2001:470::/32 Hurricane Electric 55 South Market St San Jose, CA
A151.80.211.212πŸ‡«πŸ‡· OVH151.80.0.0/16
PTRip212.ip-151-80-211.ip4.network
NS1.011001000110111001110011.com
A2400:8902:e001:10c::1πŸ‡―πŸ‡΅ AKAMAI-LINODE-AP2400:8902::/32 Akamai Technologies
PTR1.011001000110111001110011.com
A172.104.104.137πŸ‡―πŸ‡΅ AKAMAI-LINODE-AP172.104.96.0/19 Akamai Technologies
PTRip137.ip-172-104-137.ip4.network
NS10.011001000110111001110011.com
A2a01:7e00:e000:212::10πŸ‡¬πŸ‡§ AKAMAI-LINODE-AP2a01:7e00::/32 Akamai Technologies
PTR10.011001000110111001110011.com
A178.79.160.235πŸ‡¬πŸ‡§ AKAMAI-LINODE-AP178.79.128.0/18 Akamai Technologies
PTRip235.ip-178-79-160.ip4.network
NS100.011001000110111001110011.com
A2600:3c01:e000:24b::100πŸ‡ΊπŸ‡Έ AKAMAI-LINODE-AP2600:3c01::/32 Akamai Technologies
PTR100.011001000110111001110011.com
A45.56.90.55πŸ‡ΊπŸ‡Έ AKAMAI-LINODE-AP45.56.80.0/20 Akamai Technologies
PTRip55.ip-45-56-90.ip4.network
NS11.011001000110111001110011.com ⚠️ Not in parent delegation
A2a01:7e00:e000:60::11πŸ‡¬πŸ‡§ AKAMAI-LINODE-AP2a01:7e00::/32 Akamai Technologies
PTR11.011001000110111001110011.com
A178.79.140.64πŸ‡¬πŸ‡§ AKAMAI-LINODE-AP178.79.128.0/18 Akamai Technologies
PTRip64.ip-178-79-140.ip4.network
MXmx1.network.sh ⭐
A94.23.154.70πŸ‡¬πŸ‡§ OVH94.23.0.0/16 ISP Paris, France
PTRip70.ip-94-23-154.ip4.network
TXTv=spf1 mx include:_spf.smtp.network ~all
SOA0.011001000110111001110011.comhostmaster@646e73.com 2026-06-04 #6

network

DNSSECπŸ”’ Signed (DS record present)
NSv0n0.nic.network ⭐
NSv0n1.nic.network
NSv0n2.nic.network
NSv0n3.nic.network
NSv2n0.nic.network
NSv2n1.nic.network
SOAv0n0.nic.networkhostmaster@donuts.email serial=1780547298

Same first word

Similar names

DNS History

12 records (6 active, 6 former)

2017201820192020202120222023202420252026NS0.011001000110111001110011.com1.011001000110111001110011.com10.011001000110111001110011.com100.011001000110111001110011.com11.011001000110111001110011.comns1.network.shns2.network.shns3.network.shns4.network.shMXmx1.network.shmx2.network.shmx3.network.sh
●NS0.011001000110111001110011.com2026-02-23 β†’ 2026-06-04 Β· 3 obs
β—‹ 2016-12-10 21:32:40
● 2026-02-23 03:02:18
● 2026-06-04 04:34:56
●NS1.011001000110111001110011.com2026-02-23 β†’ 2026-06-04 Β· 3 obs
β—‹ 2016-12-10 21:32:40
● 2026-02-23 03:02:18
● 2026-06-04 04:34:56
●NS10.011001000110111001110011.com2026-02-23 β†’ 2026-06-04 Β· 3 obs
β—‹ 2016-12-10 21:32:40
● 2026-02-23 03:02:18
● 2026-06-04 04:34:56
●NS100.011001000110111001110011.com2026-02-23 β†’ 2026-06-04 Β· 3 obs
β—‹ 2016-12-10 21:32:40
● 2026-02-23 03:02:18
● 2026-06-04 04:34:56
●NS11.011001000110111001110011.com2026-02-23 β†’ 2026-06-04 Β· 3 obs
β—‹ 2016-12-10 21:32:40
● 2026-02-23 03:02:18
● 2026-06-04 04:34:56
β—‹NSns1.network.sh2016-12-10 β†’ 2016-12-10 Β· 3 obs
● 2016-12-10 21:32:40
β—‹ 2026-02-23 03:02:18
β—‹ 2026-06-04 04:34:56
β—‹NSns2.network.sh2016-12-10 β†’ 2016-12-10 Β· 3 obs
● 2016-12-10 21:32:40
β—‹ 2026-02-23 03:02:18
β—‹ 2026-06-04 04:34:56
β—‹NSns3.network.sh2016-12-10 β†’ 2016-12-10 Β· 3 obs
● 2016-12-10 21:32:40
β—‹ 2026-02-23 03:02:18
β—‹ 2026-06-04 04:34:56
β—‹NSns4.network.sh2016-12-10 β†’ 2016-12-10 Β· 3 obs
● 2016-12-10 21:32:40
β—‹ 2026-02-23 03:02:18
β—‹ 2026-06-04 04:34:56
●MXmx1.network.sh2026-02-23 β†’ 2026-06-04 Β· 3 obs
β—‹ 2016-12-10 21:32:40
● 2026-02-23 03:02:18
● 2026-06-04 04:34:56
β—‹MXmx2.network.sh2016-12-10 β†’ 2016-12-10 Β· 3 obs
● 2016-12-10 21:32:40
β—‹ 2026-02-23 03:02:18
β—‹ 2026-06-04 04:34:56
β—‹MXmx3.network.sh2016-12-10 β†’ 2016-12-10 Β· 3 obs
● 2016-12-10 21:32:40
β—‹ 2026-02-23 03:02:18
β—‹ 2026-06-04 04:34:56

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
networkv0n3.nic.network, v0n2.nic.network, v2n1.nic.network, v0n0.nic.network...-
ip4.network0.011001000110111001110011.com, 1.011001000110111001110011.com, 10.011001000110111001110011.com, 11.011001000110111001110011.com-

βœ… Authoritative Response

Server:178.79.160.235

NS records: 0.011001000110111001110011.com, 1.011001000110111001110011.com, 10.011001000110111001110011.com, 11.011001000110111001110011.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ip4.network (unsigned zone)

⏱️ Timing

Total: 670ms | Queries: -

πŸ“„ Records

TypeCountSample Data
NS50.011001000110111001110011.com, 10.011001000110111001110011.com...
MX1mx1.network.sh (pri: 10)
TXT1v=spf1 mx include:_spf.smtp.network ~all
SOA10.011001000110111001110011.com hostmaste

Analysis

Name Servers

The zone ip4.network is authoritative on 5 name servers: 0.011001000110111001110011.com, 100.011001000110111001110011.com, 10.011001000110111001110011.com and two additional ones.

At least some of ip4.network's name servers are shared with other domains, for example network.sh, tunnel.network, email.sh and two more.

These name servers tend to be deployed in combination with the name servers 11.011001000110111001110011.com and 1.011001000110111001110011.com.

Host names pointing to two IP addresses:

0.011001000110111001110011.com resolves to two addresses: 151.80.211.212 and 2001:470:1f13:15f::8888.

100.011001000110111001110011.com resolves to two addresses: 45.56.90.55 and 2600:3c01:e000:24b::100.

10.011001000110111001110011.com resolves to two addresses: 178.79.160.235 and 2a01:7e00:e000:212::10.

11.011001000110111001110011.com resolves to two addresses: 178.79.140.64 and 2a01:7e00:e000:60::11.

1.011001000110111001110011.com resolves to two addresses: 172.104.104.137 and 2400:8902:e001:10c::1.

Mail Servers

ip4.network uses one mail server β€” mx1.network.sh.

ip4.network has an identical mail server setup to network.sh, tunnel.network, computer.sh and 587.email, as well as other domains.

mx1.network.sh carries a single IP number, which is 94.23.154.70.