getnibble.dev - robtex.com
getnibble.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
Similar names
Previous names
Next names
DNS History
6 records (6 active, 0 former)
βNSns1bqx.name.com2026-11-04 β 2026-11-10 Β· 2 obs
β 2026-11-10 17:39:40
βNSns2nsy.name.com2026-11-04 β 2026-11-10 Β· 2 obs
β 2026-11-10 17:39:40
βNSns3sxz.name.com2026-11-04 β 2026-11-10 Β· 2 obs
β 2026-11-10 17:39:40
βNSns4cpw.name.com2026-11-04 β 2026-11-10 Β· 2 obs
β 2026-11-10 17:39:40
βA45.76.106.2112026-11-04 β 2026-11-10 Β· 2 obs
β 2026-11-10 17:39:40
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com... | - |
| getnibble.dev | ns1bqx.name.com, ns3sxz.name.com, ns4cpw.name.com, ns2nsy.name.com | - |
β Authoritative Response
Server:163.114.216.17
NS records: ns1bqx.name.com, ns3sxz.name.com, ns4cpw.name.com, ns2nsy.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for getnibble.dev (unsigned zone)
β±οΈ Timing
Total: 2048ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.76.106.211 |
| NS | 4 | ns1bqx.name.com, ns2nsy.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
IP Addresses
getnibble.dev resolves to just one IP address, 45.76.106.211.
Name Servers
getnibble.dev delegates to five name servers: ns1.name.com, ns1bqx.name.com, ns2nsy.name.com and two others.
At least some of getnibble.dev's name servers are shared with other domains, for example alliedexteriorsservices.com, thebossinc.com, luxurywashroomrental.com and two more.
These name servers tend to co-occur with ns4cpw.name.com, ns3sxz.name.com, ns2fln.name.com and 7 other name servers in the same DNS delegations.
Host names that have two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1bqx.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.
ns3sxz.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4cpw.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1bqx.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1bqx.name.com resolve to 163.114.216.17 IP addresses each.