token-tracker.dev - dns.ninja
token-tracker.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
token-tracker.dev |
token-tracker.pages.dev |
token-tracker.app |
Previous names
Next names
DNS History
5 records (5 active, 0 former)
βNSns1hwy.name.com2026-09-25 β 2026-09-26 Β· 2 obs
β 2026-09-26 23:01:54
βNSns2fln.name.com2026-09-25 β 2026-09-26 Β· 2 obs
β 2026-09-26 23:01:54
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | - |
| token-tracker.dev | ns2fln.name.com, ns3fqs.name.com, ns1hwy.name.com, ns4jnz.name.com | - |
β Authoritative Response
Server:163.114.216.49
NS records: ns2fln.name.com, ns3fqs.name.com, ns1hwy.name.com, ns4jnz.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for token-tracker.dev (unsigned zone)
β±οΈ Timing
Total: 738ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1hwy.name.com, ns2fln.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
Analysis
Name Servers
token-tracker.dev has five name servers, which are ns1.name.com, ns1hwy.name.com, ns2fln.name.com and two others.
token-tracker.dev has at least partial name server overlap with other domains, such as respiralibrepro.com, asg.team, 791.tel and two others.
ns4jnz.name.com, ns3fqs.name.com and ns3bfm.name.com β plus 7 other name servers β are commonly paired with these name servers.
Hostnames that resolve to two IP addresses:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1hwy.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2fln.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3fqs.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4jnz.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1hwy.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1hwy.name.com each resolve to 163.114.216.17 IP addresses.