whycode666.com - dns.ninja
whycode666.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 191.214.251.134🇧🇷 UNSPECIFIED160.0.0.0/3 | ||||||
| NS | ns1.julydns.com ⭐ | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.julydns.com | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.julydns.commaster@jmdns.com serial=1788322314 | ||||||
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=1788687963 | ||||||
Same first word
whycode666.com |
Previous names
Next names
DNS History
4 records (3 active, 1 former)
●NSns1.julydns.com2026-08-21 → 2026-09-06 · 2 obs
● 2026-09-06 10:13:00
●NSns2.julydns.com2026-08-21 → 2026-09-06 · 2 obs
● 2026-09-06 10:13:00
●A191.214.251.1342026-09-02 → 2026-09-06 · 3 obs
● 2026-09-02 20:03:18
● 2026-09-06 10:13:00
○A45.207.99.2032026-08-21 → 2026-08-21 · 3 obs
○ 2026-09-02 20:03:18
○ 2026-09-06 10:13:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| whycode666.com | ns1.julydns.com, ns2.julydns.com | 2 records |
✅ Authoritative Response
Server:162.159.48.223
NS records: ns1.julydns.com, ns2.julydns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for whycode666.com (unsigned zone)
⏱️ Timing
Total: 870ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 191.214.251.134 |
| NS | 2 | ns1.julydns.com, ns2.julydns.com |
| SOA | 1 | ns1.julydns.com master.jmdns.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.julydns.com, ns2.julydns.com)
Analysis
IP Addresses
whycode666.com resolves to just one IP address, 191.214.251.134.
Two other host names, along with gc-rb88.com.cn, 51zhimo.com and pmvzd9697.com.cn, also share IP numbers with whycode666.com.
Name Servers
Two name servers handle the delegation for whycode666.com: ns1.julydns.com and ns2.julydns.com.
whycode666.com shares its NS records with other domains, for example xinggangwenhua.top, lv29.com, 86steel.com and two others.
whycode666.com partially shares its NS delegation with several other domains, including lp63.com, 385mall.com, mbb77.cn and two others.
The name servers ns1.judns.com, ns2.judns.com, ns1.onclouddns.com and ns2.onclouddns.com are often found in use alongside these name servers.
ns1.julydns.com directs to 162.159.48.223, as does ns2.julydns.com — both hostnames resolve to that one IP address.
ns1.julydns.com along with ns2.julydns.com each resolve to 162.159.48.223 IP addresses.