tokenkey.dev - dns.ninja
tokenkey.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
tokenkey.io |
tokenkey.ru |
tokenkey.dev |
tokenkey.site |
tokenkey.uk |
tokenkey.plus |
tokenkey.vip |
tokenkey.xin |
tokenkey.xyz |
tokenkey.app |
tokenkey.com |
tokenkey.casa |
tokenkey.org |
tokenkey.net |
tokenkey.pro |
tokenkey.in |
Similar names
keytoken.ai |
keytoken.net |
teknokey.net |
keytoken.top |
kotenyek.hu |
teknokey.com |
teknoyek.com |
keytoken.io |
kentokey.com |
teknokey.com.tr |
keytoken.xyz |
netkeyok.workers.dev |
keytoken.com |
Previous names
Next names
DNS History
10 records (10 active, 0 former)
●NScuritiba.ns.porkbun.com2026-08-21 → 2026-09-21 · 2 obs
● 2026-09-21 03:49:10
●NSfortaleza.ns.porkbun.com2026-08-21 → 2026-09-21 · 2 obs
● 2026-09-21 03:49:10
●NSmaceio.ns.porkbun.com2026-08-21 → 2026-09-21 · 2 obs
● 2026-09-21 03:49:10
●NSsalvador.ns.porkbun.com2026-08-21 → 2026-09-21 · 2 obs
● 2026-09-21 03:49:10
●MXalt1.aspmx.l.google.com2026-08-21 → 2026-09-21 · 2 obs
● 2026-09-21 03:49:10
●MXalt2.aspmx.l.google.com2026-08-21 → 2026-09-21 · 2 obs
● 2026-09-21 03:49:10
●MXalt3.aspmx.l.google.com2026-08-21 → 2026-09-21 · 2 obs
● 2026-09-21 03:49:10
●MXalt4.aspmx.l.google.com2026-08-21 → 2026-09-21 · 2 obs
● 2026-09-21 03:49:10
●MXaspmx.l.google.com2026-08-21 → 2026-09-21 · 2 obs
● 2026-09-21 03:49:10
●A34.194.234.882026-08-21 → 2026-09-21 · 2 obs
● 2026-09-21 03:49:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| dev | ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com... | - |
| tokenkey.dev | curitiba.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com, fortaleza.ns.porkbun.com | - |
✅ Authoritative Response
Server:173.245.58.37
NS records: curitiba.ns.porkbun.com, maceio.ns.porkbun.com, salvador.ns.porkbun.com, fortaleza.ns.porkbun.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tokenkey.dev (unsigned zone)
⏱️ Timing
Total: 1610ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 34.194.234.88 |
| NS | 4 | curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=IebHgSJ1X7Y5g0X, v=spf1 include:amazonses.com -all |
| SOA | 1 | curitiba.ns.porkbun.com dns.cloudflare.c |
Analysis
IP Addresses
tokenkey.dev has exactly one IP address — 34.194.234.88.
Name Servers
Four name servers handle the delegation for tokenkey.dev: curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com and salvador.ns.porkbun.com.
tokenkey.dev shares at least some of its name servers with other domains, including mu-king.info, mancavexl.com, endfieldlab.info and two others.
The host names curitiba.ns.porkbun.com, fortaleza.ns.porkbun.com, maceio.ns.porkbun.com and salvador.ns.porkbun.com each resolve to two IP addresses: curitiba.ns.porkbun.com resolves to 173.245.58.37 and 2400:cb00:2049:1::adf5:3a25; fortaleza.ns.porkbun.com resolves to 162.159.8.140 and 2400:cb00:2049:1::a29f:88c; maceio.ns.porkbun.com resolves to 162.159.11.180 and 2400:cb00:2049:1::a29f:bb4; salvador.ns.porkbun.com resolves to 162.159.10.150 and 2400:cb00:2049:1::a29f:a96.
Mail Servers
Mail for tokenkey.dev is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by tokenkey.dev are shared with other domains: svkdcw.ac.in, shavehearth.com, serecuador.com.ec and two others among them.
These mail servers often appear in conjunction with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx3.googlemail.com and aspmx2.googlemail.com.
Host names pointing to two IP addresses:
aspmx.l.google.com points to 142.250.31.27 and 2607:f8b0:4004:c06::1b.
alt1.aspmx.l.google.com points to 192.178.234.26 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com points to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com points to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com points to 172.253.157.26 and 2a00:1450:400c:c23::1b.