forz.io - robtex.com
forz.io
io
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.nic.io ⭐ 🔒 | ||||||
| NS | a2.nic.io 🔒 | ||||||
| NS | b0.nic.io 🔒 | ||||||
| NS | c0.nic.io 🔒 | ||||||
| SOA | a0.nic.iohostmaster@donuts.email serial=1771291657 | ||||||
Up
www.forz.io |
Same first word
Similar names
zfor.cn |
zorf.com |
zorf.net |
fozr.fr |
froz.ru |
rfzo.com |
rfoz.ru |
zfor.com |
rfoz.com |
rfzo.de |
ozrf.com |
zrof.cn |
frzo.com |
fozr.com |
rzfo.cn |
rfzo.rs |
frzo.hu |
zorf.nl |
DNS History
13 records (13 active, 0 former)
●NSlex.ns.cloudflare.com2026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●NSmeiling.ns.cloudflare.com2026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●MXalt1.aspmx.l.google.com2026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●MXalt2.aspmx.l.google.com2026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●MXalt3.aspmx.l.google.com2026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●MXalt4.aspmx.l.google.com2026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●MXaspmx.l.google.com2026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●A104.26.4.1122026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●A104.26.5.1122026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●A172.67.72.392026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●A2606:4700:20::681a:4702026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●A2606:4700:20::681a:5702026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
●A2606:4700:20::ac43:48272026-02-20 → 2026-02-27 · 2 obs
● 2026-02-27 07:08:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| io | c0.nic.io, a2.nic.io, a0.nic.io, b0.nic.io | - |
| forz.io | meiling.ns.cloudflare.com, lex.ns.cloudflare.com | - |
✅ Authoritative Response
Server: 172.64.34.254
NS records: meiling.ns.cloudflare.com, lex.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for forz.io (unsigned zone)
⏱️ Timing
Total: 599ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 3 | 104.26.5.112, 172.67.72.39... |
| AAAA | 3 | 2606:4700:20::681a:470, 2606:4700:20::ac43:4827... |
| NS | 2 | lex.ns.cloudflare.com, meiling.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=b6(0x464170)PbWrD_6kFz, v=spf1 include:_spf.google.com include:s |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h2"] |
| SOA | 1 | lex.ns.cloudflare.com dns.cloudflare.com |
AI analysis
The parent of www.forz.io is forz.io.
forz.io resolves to six IP numbers: 2606:4700:20::681a:470, 2606:4700:20::681a:570, 2606:4700:20::ac43:4827, 104.26.4.112, 104.26.5.112 and 172.67.72.39.
Other host names, for instance www.codesfortomorrow.com, srv1.fr-fans.nl, surplusrecord.net, clearedgeinnovation.com.cdn.cloudflare.net and beetronics.se share IP numbers with forz.io.
Two name servers lex.ns.cloudflare.com and meiling.ns.cloudflare.com handle delegation for forz.io.
forz.io uses the same name server setup as other domains, for example ppcashout4you.xyz, educationsuniversity.com, fnet.com.br, berkeley100.com and chutlunds1.com.
forz.io partially shares name servers with other domains; examples include mpdservice.com.br, fsaodss.com, cleaners-bow.com, oxygen-v.cn and aed24.ru.
These name servers are commonly used with aron.ns.cloudflare.com, theo.ns.cloudflare.com and zoe.ns.cloudflare.com.
Host names with six IP numbers: lex.ns.cloudflare.com points to: 2606:4700:58::adf5:3bc4, 2803:f800:50::6ca2:c1c4, 2a06:98c1:50::ac40:21c4, 108.162.193.196, 172.64.33.196 and 173.245.59.196; meiling.ns.cloudflare.com points to: 2606:4700:50::a29f:26fe, 2803:f800:50::6ca2:c2fe, 2a06:98c1:50::ac40:22fe, 108.162.194.254, 162.159.38.254 and 172.64.34.254.
Five mail servers handle forz.io: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
forz.io shares some mail servers with other domains, at least partially, such as ns500742.ns500731.ns500671.ns500742.ns500731.ns500705.ns500704.ns500705.ns500678.ns500688.ns500678.ns500142.lusty(0x736c7574)z.com, ns500759.ns500698.ns500698.ns500735.ns500698.ns500698.ns500708.ns500576.ns500576.ns500698.ns500619.ns500619.ns500619.trackreceptor.com, ns500765.ns500693.ns500734.ns500699.ns500699.ns500683.ns500588.ns500588.ns500588.ns500612.ns500588.ns500578.ns500110.dtrkdll.com, ns500765.ns500699.ns500699.ns500699.ns500734.ns500693.ns500699.ns500699.ns500699.ns500693.ns500588.ns500588.ns500699.ns500693.ns500699.ns500602.dtrkdll.com and ns500759.ns500698.ns500759.ns500736.ns500736.ns500736.ns500735.ns500698.ns500698.ns500708.ns500698.ns500708.trackreceptor.com.
these mail servers are often used alongside aspmx2.googlemail.com, aspmx3.googlemail.com and aspmx4.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to: 2607:f8b0:4004:c19::1b and 172.253.62.27
alt1.aspmx.l.google.com points to: 2607:f8b0:4003:c30::1b and 74.125.27.26
alt2.aspmx.l.google.com points to: 2607:f8b0:4001:c70::1a and 192.178.209.26
alt3.aspmx.l.google.com points to: 2607:f8b0:4024:c0d::1b and 192.178.152.26
alt4.aspmx.l.google.com points to: 2607:f8b0:4023:403::1a and 142.250.96.27