whykingz.com - robtex.com
whykingz.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1771291435 | ||||||
Same first word
whykingz.com |
DNS History
14 records (11 active, 3 former)
●NSemely.ns.cloudflare.com2026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
●NSjihoon.ns.cloudflare.com2026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
○NSns13.domaincontrol.com2019-12-14 → 2019-12-14 · 2 obs
○ 2026-02-22 20:14:36
○NSns14.domaincontrol.com2019-12-14 → 2019-12-14 · 2 obs
○ 2026-02-22 20:14:36
●MXalt1.aspmx.l.google.com2019-12-14 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
●MXalt2.aspmx.l.google.com2019-12-14 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
●MXaspmx.l.google.com2019-12-14 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
●MXaspmx2.googlemail.com2019-12-14 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
●MXaspmx3.googlemail.com2019-12-14 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
●A104.21.52.632026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
●A172.67.196.522026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
○A184.168.221.482019-12-14 → 2019-12-14 · 2 obs
○ 2026-02-22 20:14:36
●A2606:4700:3037::6815:343f2026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
●A2606:4700:3037::ac43:c4342026-02-22 → 2026-02-22 · 2 obs
● 2026-02-22 20:14:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| whykingz.com | emely.ns.cloudflare.com, jihoon.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server: 108.162.194.209
NS records: emely.ns.cloudflare.com, jihoon.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for whykingz.com (unsigned zone)
⏱️ Timing
Total: 202ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 172.67.196.52, 104.21.52.63 |
| AAAA | 2 | 2606:4700:3037::ac43:c434, 2606:4700:3037::6815:343f |
| NS | 2 | emely.ns.cloudflare.com, jihoon.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), aspmx2.googlemail.com (pri: 10)... |
| TXT | 5 | MS=102F4E93CC094ABE5F0984E31FBD866761986, atlassian-domain-verification=8Dw2U4/07n... |
| HTTPS | 1 | {"priority":1,"target":".","alpn":["h3", |
| SOA | 1 | emely.ns.cloudflare.com dns.cloudflare.c |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (emely.ns.cloudflare.com, emely.ns.cloudflare.com, emely.ns.cloudflare.com...)
AI analysis
whykingz.com maps to four IP numbers: 2606:4700:3037::6815:343f, 2606:4700:3037::ac43:c434, 104.21.52.63 and 172.67.196.52.
Other host names such as ilssepe.com, www.scsxhj.com, divislift.click, pureprecisionfitness.club and cornstick.com share IPs with whykingz.com.
Two name servers emely.ns.cloudflare.com and jihoon.ns.cloudflare.com handle the delegation for whykingz.com.
whykingz.com shares the same name server setup as other domains, for example championglobal.net, campusmarketer.com, learngraphql.com, championworld.net and tamr.cloud.
whykingz.com at least partially shares name servers with other domains, for example mirhelp.com, lplabo.net, seckey.com, microblet.com and efpp.info.
These name servers are often used together with johnathan.ns.cloudflare.com and alice.ns.cloudflare.com.
Host names with six IP numbers:
emely.ns.cloudflare.com points to 2606:4700:50::a29f:26d1, 2803:f800:50::6ca2:c2d1, 2a06:98c1:50::ac40:22d1, 108.162.194.209, 162.159.38.209 and 172.64.34.209.
jihoon.ns.cloudflare.com points to 2606:4700:58::a29f:2ce9, 2803:f800:50::6ca2:c3e9, 2a06:98c1:50::ac40:23e9, 108.162.195.233, 162.159.44.233 and 172.64.35.233.
whykingz.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
whykingz.com shares at least partially some mail servers with other domains, for instance bimnine.com, olympia.chat, andoverfabrics.com, studerende.dk and ns500759.ns500698.ns500698.ns500698.ns500736.ns500736.ns500736.ns500698.ns500736.ns500698.ns500708.ns500708.ns500576.ns500576.ns500576.ns500619.ns500619.trackreceptor.com.
these mail servers are often used together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IPs
The host name aspmx2.googlemail.com points to 2607:f8b0:4003:c30::1b and 74.125.27.27.
The host name aspmx3.googlemail.com points to 2607:f8b0:4001:c70::1a and 192.178.209.27.
The host name aspmx.l.google.com points to 2607:f8b0:4004:c19::1b and 172.253.62.27.
The host name alt1.aspmx.l.google.com points to 2607:f8b0:4003:c30::1b and 74.125.27.26.
The host name alt2.aspmx.l.google.com points to 2607:f8b0:4001:c70::1a and 192.178.209.26.
Host names pointing to 2607:f8b0:4003:c30::1b are aspmx2.googlemail.com and alt1.aspmx.l.google.com.
Host names pointing to 2607:f8b0:4001:c70::1a are aspmx3.googlemail.com and alt2.aspmx.l.google.com.
Common IPs: 2607:f8b0:4003:c30::1b used by aspmx2.googlemail.com and alt1.aspmx.l.google.com; 2607:f8b0:4001:c70::1a used by aspmx3.googlemail.com and alt2.aspmx.l.google.com.