0nez.com - robtex.com
0nez.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.dyna-ns.net ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::a29f:1a5c🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1b9e🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.92Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 162.159.27.158Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.dyna-ns.net ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::a29f:1805🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1905🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.24.5Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 162.159.25.5Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
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.netnstld@verisign-grs.com serial=1784478152 | ||||||
Same first word
0nez.com |
Similar names
z0ne.social |
0zen.org |
z0ne.moe |
z0ne.dev |
z0ne.email |
zen0.lat |
0zen.com |
zen0.net |
zen0.de |
0nze.com |
z0ne.ru |
0zen.co |
zen0.fr |
zen0.nl |
DNS History
14 records (2 active, 12 former)
○NSns1.above.com2016-03-13 → 2017-07-01 · 5 obs
○ 2016-01-07 04:50:50
● 2016-03-13 00:44:10
● 2017-07-01 19:23:02
○ 2026-06-30 17:45:58
○ 2026-07-19 16:25:20
● 2016-03-13 00:44:10
● 2017-07-01 19:23:02
○ 2026-06-30 17:45:58
○ 2026-07-19 16:25:20
○NSns1.dsredirection.com2015-08-22 → 2016-01-07 · 4 obs
● 2015-08-22 19:45:00
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
●NSns1.dyna-ns.net2026-06-30 → 2026-07-19 · 3 obs
○ 2017-07-01 19:23:02
● 2026-06-30 17:45:58
● 2026-07-19 16:25:20
● 2026-06-30 17:45:58
● 2026-07-19 16:25:20
○NSns2.above.com2016-03-13 → 2017-07-01 · 5 obs
○ 2016-01-07 04:50:50
● 2016-03-13 00:44:10
● 2017-07-01 19:23:02
○ 2026-06-30 17:45:58
○ 2026-07-19 16:25:20
● 2016-03-13 00:44:10
● 2017-07-01 19:23:02
○ 2026-06-30 17:45:58
○ 2026-07-19 16:25:20
○NSns2.dsredirection.com2015-08-22 → 2016-01-07 · 4 obs
● 2015-08-22 19:45:00
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
●NSns2.dyna-ns.net2026-06-30 → 2026-07-19 · 3 obs
○ 2017-07-01 19:23:02
● 2026-06-30 17:45:58
● 2026-07-19 16:25:20
● 2026-06-30 17:45:58
● 2026-07-19 16:25:20
○MXmail.post-host.net2016-03-13 → 2016-07-11 · 4 obs
● 2016-03-13 00:44:10
● 2016-07-11 23:51:44
○ 2016-12-10 13:28:30
○ 2026-07-19 16:25:20
● 2016-07-11 23:51:44
○ 2016-12-10 13:28:30
○ 2026-07-19 16:25:20
○MXmx92.m1bp.com2017-07-01 → 2017-07-01 · 4 obs
○ 2016-12-10 13:28:30
● 2017-07-01 19:23:02
○ 2026-06-30 17:45:58
○ 2026-07-19 16:25:20
● 2017-07-01 19:23:02
○ 2026-06-30 17:45:58
○ 2026-07-19 16:25:20
○MXmx92.mb5p.com2017-07-01 → 2017-07-01 · 4 obs
○ 2016-12-10 13:28:30
● 2017-07-01 19:23:02
○ 2026-06-30 17:45:58
○ 2026-07-19 16:25:20
● 2017-07-01 19:23:02
○ 2026-06-30 17:45:58
○ 2026-07-19 16:25:20
○A103.224.182.2402016-03-13 → 2017-07-01 · 5 obs
○ 2016-01-07 04:50:50
● 2016-03-13 00:44:10
● 2017-07-01 19:23:02
○ 2026-06-30 17:45:58
○ 2026-07-19 16:25:20
● 2016-03-13 00:44:10
● 2017-07-01 19:23:02
○ 2026-06-30 17:45:58
○ 2026-07-19 16:25:20
○A208.73.210.2002015-08-22 → 2016-01-07 · 4 obs
● 2015-08-22 19:45:00
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
○A208.73.210.2142015-08-22 → 2016-01-07 · 4 obs
● 2015-08-22 19:45:00
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
○A208.73.210.2172015-08-22 → 2016-01-07 · 4 obs
● 2015-08-22 19:45:00
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
○A208.73.211.1782015-08-22 → 2016-01-07 · 4 obs
● 2015-08-22 19:45:00
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
● 2016-01-07 04:50:50
○ 2016-03-13 00:44:10
○ 2026-07-19 16:25:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, m.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net... | - |
| 0nez.com | ns2.dyna-ns.net, ns1.dyna-ns.net | - |
✅ Authoritative Response
Server:162.159.26.92
NS records: ns2.dyna-ns.net, ns1.dyna-ns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 0nez.com (unsigned zone)
⏱️ Timing
Total: 3526ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
0nez.com uses two name servers for its delegation: ns1.dyna-ns.net and ns2.dyna-ns.net.
0nez.com has the same name server delegation as a number of other domains, such as 2142o.com, radarcom.com, kanavla.com and two more.
At least some of 0nez.com's name servers are also used by other domains, among them floary.com.
The hosts ns1.dyna-ns.net and ns2.dyna-ns.net each resolve to four IP numbers: ns1.dyna-ns.net directs to 162.159.26.92, 162.159.27.158, 2400:cb00:2049:1::a29f:1a5c and 2400:cb00:2049:1::a29f:1b9e, and ns2.dyna-ns.net directs to 162.159.24.5, 162.159.25.5, 2400:cb00:2049:1::a29f:1805 and 2400:cb00:2049:1::a29f:1905.