sn667.com - robtex.com
sn667.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.ttfcdns.com ⚠️ Not in zone NS records | ||||||
| NS | ns2.ttfcdns.com ⚠️ Not in zone NS records | ||||||
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
sn667.com |
DNS History
5 records (2 active, 3 former)
●NSns1.ttfcdns.com2026-03-12 → 2026-03-14 · 3 obs
○ 2017-11-14 14:39:00
● 2026-03-12 21:14:30
● 2026-03-14 01:51:26
● 2026-03-12 21:14:30
● 2026-03-14 01:51:26
○NSns1.ttfcvns.com2017-11-14 → 2017-11-14 · 3 obs
● 2017-11-14 14:39:00
○ 2026-03-12 21:14:30
○ 2026-03-14 01:51:26
○ 2026-03-12 21:14:30
○ 2026-03-14 01:51:26
●NSns2.ttfcdns.com2026-03-12 → 2026-03-14 · 3 obs
○ 2017-11-14 14:39:00
● 2026-03-12 21:14:30
● 2026-03-14 01:51:26
● 2026-03-12 21:14:30
● 2026-03-14 01:51:26
○NSns2.ttfcvns.com2017-11-14 → 2017-11-14 · 3 obs
● 2017-11-14 14:39:00
○ 2026-03-12 21:14:30
○ 2026-03-14 01:51:26
○ 2026-03-12 21:14:30
○ 2026-03-14 01:51:26
○A43.229.36.592017-11-14 → 2017-11-14 · 3 obs
● 2017-11-14 14:39:00
○ 2026-03-12 21:14:30
○ 2026-03-14 01:51:26
○ 2026-03-12 21:14:30
○ 2026-03-14 01:51:26
🔍 DNS Trace
Analysis
Name Servers
sn667.com is delegated to two name servers ns1.ttfcdns.com and ns2.ttfcdns.com.
sn667.com shares the same name server setup as other domains, for instance 925099.com, kg772.com, zn559.com, bt661.com and 19200d.com.