leafbyte.dev - robtex.com
leafbyte.dev
dev
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns-tld1.charlestonroadregistry.com ⭐ | ||||||
| NS | ns-tld2.charlestonroadregistry.com | ||||||
| NS | ns-tld3.charlestonroadregistry.com | ||||||
| NS | ns-tld4.charlestonroadregistry.com | ||||||
| NS | ns-tld5.charlestonroadregistry.com | ||||||
| SOA | ns-tld1.charlestonroadregistry.comcloud-dns-hostmaster@google.com serial=1 | ||||||
Same first word
leafbyte.dev |
leafbyte.cn |
leafbyte.ru |
leafbyte.id |
leafbyte.ai |
leafbyte.com.ph |
leafbyte.ltd |
leafbyte.com |
leafbyte.asia |
leafbyte.biz.id |
leafbyte.ph |
Similar names
Previous names
Next names
DNS History
6 records (6 active, 0 former)
●A173.212.228.2132026-10-02 → 2026-11-20 · 2 obs
● 2026-11-20 18:36:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | - |
| leafbyte.dev | ns1bcp.name.com, ns4qxz.name.com, ns3gxy.name.com, ns2nsy.name.com | - |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1bcp.name.com, ns4qxz.name.com, ns3gxy.name.com, ns2nsy.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for leafbyte.dev (unsigned zone)
⏱️ Timing
Total: 968ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 173.212.228.213 |
| NS | 4 | ns1bcp.name.com, ns2nsy.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
IP Addresses
leafbyte.dev has exactly one IP address — 173.212.228.213.
Name Servers
Five name servers handle delegation for leafbyte.dev: ns1.name.com, ns1bcp.name.com, ns2nsy.name.com and two others.
There is at least partial name server overlap between leafbyte.dev and other domains — trylaunchready.com, fafplrr236h3b.xyz, qm9275.com and two more among them.
These name servers regularly appear alongside ns3gxy.name.com, ns4qxz.name.com, ns1hwy.name.com and 7 other name servers in NS record sets.
Host names pointing to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1bcp.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2nsy.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3gxy.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4qxz.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1bcp.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1bcp.name.com resolve to 163.114.216.17 IP addresses each.