betsignals.io - robtex.com
betsignals.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=1786082464 | ||||||
Same first word
betsignals.io |
betsignals.vip |
Similar names
DNS History
8 records (8 active, 0 former)
●NScoby.ns.cloudflare.com2026-08-02 → 2026-08-07 · 2 obs
● 2026-08-07 06:07:46
●NSelly.ns.cloudflare.com2026-08-02 → 2026-08-07 · 2 obs
● 2026-08-07 06:07:46
●MXeforward1.registrar-servers.com2026-08-02 → 2026-08-07 · 2 obs
● 2026-08-07 06:07:46
●MXeforward2.registrar-servers.com2026-08-02 → 2026-08-07 · 2 obs
● 2026-08-07 06:07:46
●MXeforward3.registrar-servers.com2026-08-02 → 2026-08-07 · 2 obs
● 2026-08-07 06:07:46
●MXeforward4.registrar-servers.com2026-08-02 → 2026-08-07 · 2 obs
● 2026-08-07 06:07:46
●MXeforward5.registrar-servers.com2026-08-02 → 2026-08-07 · 2 obs
● 2026-08-07 06:07:46
●A169.58.97.802026-08-02 → 2026-08-07 · 2 obs
● 2026-08-07 06:07:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| io | a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io | - |
| betsignals.io | coby.ns.cloudflare.com, elly.ns.cloudflare.com | - |
✅ Authoritative Response
Server:108.162.193.92
NS records: coby.ns.cloudflare.com, elly.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for betsignals.io (unsigned zone)
⏱️ Timing
Total: 616ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 169.58.97.80 |
| NS | 2 | coby.ns.cloudflare.com, elly.ns.cloudflare.com |
| MX | 5 | eforward1.registrar-servers.com (pri: 10, eforward2.registrar-servers.com (pri: 10... |
| TXT | 2 | google-site-verification=1oDen3KY1MG7Ipz, v=spf1 include:spf.efwd.registrar-server |
| SOA | 1 | coby.ns.cloudflare.com dns.cloudflare.co |
Analysis
IP Addresses
betsignals.io has exactly one IP address — 169.58.97.80.
Name Servers
The NS records for betsignals.io delegate to coby.ns.cloudflare.com and elly.ns.cloudflare.com.
The name server configuration of betsignals.io is shared with other domains, for instance djina.com, hotvog.com, shirts.biz and two others.
There is at least partial name server overlap between betsignals.io and other domains — rezydev.com, connecticuteldercareguide.com, studio-ginkgo.ch and two more among them.
The name servers jasper.ns.cloudflare.com, jaime.ns.cloudflare.com and aliza.ns.cloudflare.com are often found in combination with these name servers.
Hosts with 6 IP addresses each:
coby.ns.cloudflare.com maps to 108.162.193.92, 172.64.33.92, 173.245.59.92 and 3 additional IP addresses.
elly.ns.cloudflare.com maps to 108.162.194.246, 162.159.38.246, 172.64.34.246 and 3 additional IP addresses.
Mail Servers
betsignals.io has five mail servers, which are eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com and two others.
At least some of the mail servers used by betsignals.io are shared with other domains: draftwizard.org, fetchlet.com, lyuba.net and two others among them.
These mail servers often appear in conjunction with the mail servers eforward5.registrar-servers.com, eforward4.registrar-servers.com, eforward6.registrar-servers.com and eforward7.registrar-servers.com.
Host names resolving to a single 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.
Three host names point to 162.255.118.51: eforward1.registrar-servers.com, eforward3.registrar-servers.com and eforward5.registrar-servers.com.
eforward2.registrar-servers.com and eforward4.registrar-servers.com each have 162.255.118.52 IP addresses.