togo.do - robtex.com
togo.do
do
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns.nic.do ⚠️ Not in zone NS records | ||||||
| NS | ns1.nic.do ⚠️ Not in zone NS records | ||||||
| NS | ns2.nic.do ⚠️ Not in zone NS records | ||||||
| NS | ns4.nic.do ⚠️ Not in zone NS records | ||||||
| NS | ns5.nic.do ⚠️ Not in zone NS records | ||||||
Same first word
Similar names
DNS History
5 records (3 active, 2 former)
●NSns1.101domain.com2026-07-07 → 2026-07-10 · 2 obs
● 2026-07-10 20:53:40
●NSns2.101domain.com2026-07-07 → 2026-07-10 · 2 obs
● 2026-07-10 20:53:40
●NSns5.101domain.com2026-07-07 → 2026-07-10 · 2 obs
● 2026-07-10 20:53:40
○MXmail.101domain.com2026-07-07 → 2026-07-07 · 2 obs
○ 2026-07-10 20:53:40
○A165.227.115.1532026-07-07 → 2026-07-07 · 2 obs
○ 2026-07-10 20:53:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| do | phloem.uoregon.edu, ns4.nic.do, a.lactld.org, ns1.nic.do... | 14 records |
| togo.do | ns5.101domain.com, ns2.101domain.com, ns1.101domain.com | - |
✅ Authoritative Response
Server:162.159.24.202
NS records: ns5.101domain.com, ns2.101domain.com, ns1.101domain.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for do (unsigned zone)
⏱️ Timing
Total: 521ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 165.227.115.153 |
| NS | 3 | NS1.101DOMAIN.COM, NS2.101DOMAIN.COM... |
| MX | 1 | MAIL.101DOMAIN.COM (pri: 10) |
| TXT | 1 | google-site-verification=8O4A39L-qCSL5v0 |
| SOA | 1 | NS1.101DOMAIN.COM ADMIN.togo.do |
📌 Glue Records Collected
Total: 14
In-bailiwick: 10 (ns5.nic.do, ns4.nic.do, ns2.nic.do...)
Out-of-bailiwick: 4 (phloem.uoregon.edu, a.lactld.org, phloem.uoregon.edu...)
Analysis
Name Servers
The authoritative name servers for togo.do are ns1.101domain.com, ns2.101domain.com and ns5.101domain.com — three in total.
There is at least partial name server overlap between togo.do and other domains — jamesbrown.design, naaisabudhabi.ae, xn--pssstv48lx7a.com and two more among them.
Hosts pointing to four IP addresses:
ns5.101domain.com resolves to four IP addresses — 162.159.24.202, 162.159.25.156, 2400:cb00:2049:1::a29f:18ca and 2400:cb00:2049:1::a29f:199c.
Hosts with two IP numbers each:
ns1.101domain.com directs traffic to 162.159.24.202 and 2400:cb00:2049:1::a29f:18ca.
ns2.101domain.com directs traffic to 162.159.25.156 and 2400:cb00:2049:1::a29f:199c.
Both ns5.101domain.com and ns1.101domain.com resolve to 2400:cb00:2049:1::a29f:18ca IP addresses each.
Both ns5.101domain.com and ns2.101domain.com resolve to 2400:cb00:2049:1::a29f:199c IP addresses each.
Both ns5.101domain.com and ns1.101domain.com resolve to 162.159.24.202 IP addresses each.
Both ns5.101domain.com and ns2.101domain.com resolve to 162.159.25.156 IP addresses each.