666.cc - robtex.com
666.cc
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.google.com ⚠️ Not in zone NS records | ||||||
| A | 2001:4860:4802:32::a🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns1.google.com | ||||||
| A | 216.239.32.10🇺🇸 Google216.239.32.0/24 | ||||||
| PTR | ns1.google.com | ||||||
| NS | ns2.google.com ⚠️ Not in zone NS records | ||||||
| A | 2001:4860:4802:34::a🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns2.google.com | ||||||
| A | 216.239.34.10🇺🇸 Google216.239.34.0/24 | ||||||
| PTR | ns2.google.com | ||||||
| NS | ns3.google.com ⚠️ Not in zone NS records | ||||||
| A | 2001:4860:4802:36::a🇺🇸 Google2001:4860::/32 | ||||||
| PTR | ns3.google.com | ||||||
| A | 216.239.36.10🇺🇸 Google216.239.36.0/24 | ||||||
| PTR | ns3.google.com | ||||||
cc
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ac1.nstld.com ⭐ | ||||||
| NS | ac2.nstld.com | ||||||
| NS | ac3.nstld.com | ||||||
| NS | ac4.nstld.com | ||||||
| SOA | ac1.nstld.cominfo@verisign-grs.com serial=1771291222 | ||||||
Same first word
DNS History
13 records (3 active, 10 former)
●NSns1.google.com2026-02-23 → 2026-02-27 · 3 obs
● 2026-02-23 02:39:40
● 2026-02-27 02:33:32
○NSns1.isp4you.at2015-08-31 → 2016-07-21 · 4 obs
● 2016-07-21 13:48:50
○ 2026-02-23 02:39:40
○ 2026-02-27 02:33:32
●NSns2.google.com2026-02-23 → 2026-02-27 · 3 obs
● 2026-02-23 02:39:40
● 2026-02-27 02:33:32
○NSns2.isp4you.at2015-08-31 → 2016-07-21 · 4 obs
● 2016-07-21 13:48:50
○ 2026-02-23 02:39:40
○ 2026-02-27 02:33:32
●NSns3.google.com2026-02-23 → 2026-02-27 · 3 obs
● 2026-02-23 02:39:40
● 2026-02-27 02:33:32
○NSns3.isp4you.at2015-08-31 → 2016-07-21 · 4 obs
● 2016-07-21 13:48:50
○ 2026-02-23 02:39:40
○ 2026-02-27 02:33:32
○NSns4.isp4you.at2015-08-31 → 2016-07-21 · 4 obs
● 2016-07-21 13:48:50
○ 2026-02-23 02:39:40
○ 2026-02-27 02:33:32
○NSns5.isp4you.at2015-08-31 → 2016-07-21 · 4 obs
● 2016-07-21 13:48:50
○ 2026-02-23 02:39:40
○ 2026-02-27 02:33:32
○MXmailwall.isp4you.at2015-08-31 → 2015-08-31 · 3 obs
○ 2015-12-13 04:12:22
○ 2026-02-27 02:33:32
○MXmx2.mailwall.cc2015-12-13 → 2016-07-21 · 5 obs
● 2015-12-13 04:12:22
● 2016-07-21 13:48:50
○ 2026-02-23 02:39:40
○ 2026-02-27 02:33:32
○A217.70.142.552015-08-31 → 2016-03-18 · 4 obs
● 2016-03-18 09:15:02
○ 2016-07-21 13:48:50
○ 2026-02-27 02:33:32
○A87.98.150.1012016-07-21 → 2016-07-21 · 4 obs
● 2016-07-21 13:48:50
○ 2026-02-23 02:39:40
○ 2026-02-27 02:33:32
○CNAME301wall-yhb.vkoopp.com2026-02-23 → 2026-02-27 · 2 obs
○ 2026-02-27 02:33:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cc | ac1.nstld.com, ac2.nstld.com, ac3.nstld.com, ac4.nstld.com | - |
| 666.cc | ns2.google.com, ns1.google.com, ns3.google.com | - |
✅ Authoritative Response
Server: 216.239.34.10
NS records: ns2.google.com, ns1.google.com, ns3.google.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 666.cc (unsigned zone)
⏱️ Timing
Total: 403ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
AI analysis
The delegation for 666.cc is handled by three name servers: ns1.google.com, ns2.google.com and ns3.google.com.
666.cc at least partially shares name servers with other domains, for instance 164.85.209.in-addr.arpa, financialleadonline.com, goog.gl, flexycore.fr and www-italyweloveyou-com.webpkgcache.com.
These name servers are commonly used with the name servers ns4.google.com.
Two IP numbers per host:
ns1.google.com points to 2001:4860:4802:32::a and 216.239.32.10.
ns2.google.com points to 2001:4860:4802:34::a and 216.239.34.10.
ns3.google.com points to 2001:4860:4802:36::a and 216.239.36.10.