nextbyte.dev - dns.ninja
nextbyte.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
nextbyte.mx |
nextbyte.com.ar |
nextbyte.net |
nextbyte.co |
nextbyte.co.tz |
nextbyte.eu |
nextbyte.com |
nextbyte.ro |
nextbyte.org |
nextbyte.com.au |
nextbyte.dev |
nextbyte.ch |
nextbyte.in |
nextbyte.hu |
nextbyte.de |
Similar names
DNS History
8 records (8 active, 0 former)
●NSdns1.registrar-servers.com2026-03-18 → 2026-06-28 · 2 obs
● 2026-06-28 23:12:40
●NSdns2.registrar-servers.com2026-03-18 → 2026-06-28 · 2 obs
● 2026-06-28 23:12:40
●MXalt1.aspmx.l.google.com2026-03-18 → 2026-06-28 · 2 obs
● 2026-06-28 23:12:40
●MXalt2.aspmx.l.google.com2026-03-18 → 2026-06-28 · 2 obs
● 2026-06-28 23:12:40
●MXaspmx.l.google.com2026-03-18 → 2026-06-28 · 2 obs
● 2026-06-28 23:12:40
●MXaspmx2.googlemail.com2026-03-18 → 2026-06-28 · 2 obs
● 2026-06-28 23:12:40
●MXaspmx3.googlemail.com2026-03-18 → 2026-06-28 · 2 obs
● 2026-06-28 23:12:40
●A109.106.250.1962026-03-18 → 2026-06-28 · 2 obs
● 2026-06-28 23:12:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld2.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com... | 10 records |
| nextbyte.dev | dns1.registrar-servers.com, dns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for nextbyte.dev (unsigned zone)
⏱️ Timing
Total: 471ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 109.106.250.196 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=CuQpBY5xRGzOniu |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 10
Out-of-bailiwick: 10 (ns-tld5.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)
Analysis
IP Addresses
nextbyte.dev resolves to just one IP address, 109.106.250.196.
Two other host names, along with tranbinh.com, sisconmx.com and liliagarza.com.mx, also share IP numbers with nextbyte.dev.
Name Servers
nextbyte.dev uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.
nextbyte.dev shares its NS records with other domains, for example beaconbird.org, traumsteinshop.com, sequi.org and two others.
The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
nextbyte.dev is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between nextbyte.dev and other domains, including cirmirakis.com, ns500821.ns500821.ns500841.ns500841.ns500841.ns500841.ns500821.ns500794.ns500821.ns500794.ns500795.ns500795.ns500794.ns500821.ns500795.ns500790.ns500795.lustypartnersfinder.com, ns500724.ns500599.ns500724.ns500737.ns500599.ns500724.ns500599.ns500599.ns500599.ns500697.ns500682.ns500669.ns500583.yummyflingsfinder.com and two others.
These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 172.253.63.26 and 2607:f8b0:4004:c1b::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.