whyichime.net - robtex.com
whyichime.net
net
| 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=1776106997 | ||||||
Same first word
whyichime.org |
whyichime.net |
whyichime.com |
DNS History
2 records (2 active, 0 former)
●NSdns1.cscdns.net2026-04-04 → 2026-04-13 · 2 obs
● 2026-04-13 19:15:38
●NSdns2.cscdns.net2026-04-04 → 2026-04-13 · 2 obs
● 2026-04-13 19:15:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | g.gtld-servers.net, f.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net... | - |
| whyichime.net | dns1.cscdns.net, dns2.cscdns.net | 4 records |
✅ Authoritative Response
Server:156.154.130.100
NS records: dns1.cscdns.net, dns2.cscdns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for whyichime.net (unsigned zone)
⏱️ Timing
Total: 168ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.cscdns.net, dns1.cscdns.net, dns2.cscdns.net...)
Analysis
Name Servers
whyichime.net is delegated to two name servers: dns1.cscdns.net and dns2.cscdns.net.
whyichime.net uses the same name server setup as other domains such as keysight.jp, lentille(0x736578)presse.fr, yves-rocher.uk, twnb.tv and explorers-hotel-disney.com.
whyichime.net shares name servers with other domains at least partially, for instance auto-rebates.com, cfc-countrywide.net and enta.dk.
These name servers are commonly used with the name servers ns101.bac.com and ns102.bac.com.
Host names with two IP numbers:
dns1.cscdns.net points to 2610:a1:1022::100 and 156.154.130.100; dns2.cscdns.net points to 2610:a1:1023::100 and 156.154.131.100.