fleetcode.io - dns.ninja
fleetcode.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=1789626694 | ||||||
Same first word
fleetcode.lk |
fleetcode.cn |
fleetcode.sh |
fleetcode.net |
fleetcode.com |
fleetcode.dev |
fleetcode.fi |
fleetcode.ai |
fleetcode.info |
fleetcode.io |
Similar names
codefleet.hu |
codefleet.ai |
codefleet.co.uk |
codefleet.us |
codefleet.com |
codefleet.info |
codefleet.app |
codefleet.io |
codefleet.net |
decofleet.mx |
efectoled.com |
Previous names
Next names
DNS History
8 records (8 active, 0 former)
●NSdns1.registrar-servers.com2026-09-10 → 2026-09-17 · 2 obs
● 2026-09-17 06:43:24
●NSdns2.registrar-servers.com2026-09-10 → 2026-09-17 · 2 obs
● 2026-09-17 06:43:24
●MXeforward1.registrar-servers.com2026-09-10 → 2026-09-17 · 2 obs
● 2026-09-17 06:43:24
●MXeforward2.registrar-servers.com2026-09-10 → 2026-09-17 · 2 obs
● 2026-09-17 06:43:24
●MXeforward3.registrar-servers.com2026-09-10 → 2026-09-17 · 2 obs
● 2026-09-17 06:43:24
●MXeforward4.registrar-servers.com2026-09-10 → 2026-09-17 · 2 obs
● 2026-09-17 06:43:24
●MXeforward5.registrar-servers.com2026-09-10 → 2026-09-17 · 2 obs
● 2026-09-17 06:43:24
●A162.255.119.1982026-09-10 → 2026-09-17 · 2 obs
● 2026-09-17 06:43:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| io | a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io | - |
| fleetcode.io | dns1.registrar-servers.com, dns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fleetcode.io (unsigned zone)
⏱️ Timing
Total: 385ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 162.255.119.198 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | eforward1.registrar-servers.com (pri: 10, eforward2.registrar-servers.com (pri: 10... |
| TXT | 1 | v=spf1 include:spf.efwd.registrar-server |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
Analysis
IP Addresses
fleetcode.io resolves to just one IP address, 162.255.119.198.
Two other host names, along with skorsky337.com, impactreel.ai and ellatrucker.com, also share IP numbers with fleetcode.io.
Name Servers
The NS records for fleetcode.io delegate to dns1.registrar-servers.com and dns2.registrar-servers.com.
fleetcode.io shares its NS records with other domains, for example gulasens.ai, supercollectorbros.com, areputation.co and two others.
dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200. Likewise, dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200 — two IP addresses apiece.
Mail Servers
Five mail servers handle fleetcode.io: eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com and two others.
There is at least a partial MX overlap between fleetcode.io and other domains, including ale-staging.com, blbook777.in, profitsbeyondsales.com and two others.
It is common to find these mail servers used together with the mail servers eforward4.registrar-servers.com and eforward5.registrar-servers.com.
Host names that point to one IP address:
eforward1.registrar-servers.com resolves to the IP address 162.255.118.51.
eforward2.registrar-servers.com resolves to the IP address 162.255.118.52.
eforward3.registrar-servers.com resolves to the IP address 162.255.118.51.
eforward4.registrar-servers.com resolves to the IP address 162.255.118.52.
eforward5.registrar-servers.com resolves to the IP address 162.255.118.51.
Each of eforward1.registrar-servers.com, eforward3.registrar-servers.com and eforward5.registrar-servers.com resolves to 162.255.118.51.
eforward2.registrar-servers.com and eforward4.registrar-servers.com each have 162.255.118.52 IP addresses.