snsdy.com - robtex.com
snsdy.com
| CNAME | a.dnsapi12.com | ||||||
| CNAME | baidu.cloudflare.182682.xyz | ||||||
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2606:4700:e7::3151:47a9🇺🇸 Cloudflare2606:4700::/36 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 2606:4700:3032::818:669e🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 2606:4700:3035::1a4f:5642🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 2606:4700:8ca0::3dc4:21a2🇺🇸 Cloudflare2606:4700:8ca0::/48 | ||||||
| A | 2a06:98c1:3120::5692:61a4🇺🇸 Cloudflare2a06:98c1:3120::/48 | ||||||
| A | 104.16.250.22Cloudflare104.16.240.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 104.17.25.173Cloudflare104.17.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 104.18.185.26Cloudflare104.18.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 104.21.224.5Cloudflare104.21.224.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| A | 104.21.227.134Cloudflare104.21.224.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
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=1778764056 | ||||||
Same first word
snsdy.com |
Similar names
DNS History
11 records (3 active, 8 former)
○NSns1.domain.com2016-03-06 → 2016-06-24 · 4 obs
● 2016-03-06 20:11:24
● 2016-06-24 08:14:32
○ 2017-02-11 23:06:20
○ 2026-05-14 13:34:04
● 2016-06-24 08:14:32
○ 2017-02-11 23:06:20
○ 2026-05-14 13:34:04
●NSns1.julydns.com2026-04-25 → 2026-05-14 · 3 obs
○ 2018-03-02 19:39:12
● 2026-04-25 22:53:18
● 2026-05-14 13:34:04
● 2026-04-25 22:53:18
● 2026-05-14 13:34:04
○NSns1.sedoparking.com2017-02-11 → 2017-02-11 · 4 obs
○ 2016-06-24 08:14:32
● 2017-02-11 23:06:20
○ 2018-03-02 19:39:12
○ 2026-05-14 13:34:04
● 2017-02-11 23:06:20
○ 2018-03-02 19:39:12
○ 2026-05-14 13:34:04
○NSns2.domain.com2016-03-06 → 2016-06-24 · 4 obs
● 2016-03-06 20:11:24
● 2016-06-24 08:14:32
○ 2017-02-11 23:06:20
○ 2026-05-14 13:34:04
● 2016-06-24 08:14:32
○ 2017-02-11 23:06:20
○ 2026-05-14 13:34:04
●NSns2.julydns.com2026-04-25 → 2026-05-14 · 3 obs
○ 2018-03-02 19:39:12
● 2026-04-25 22:53:18
● 2026-05-14 13:34:04
● 2026-04-25 22:53:18
● 2026-05-14 13:34:04
○NSns2.sedoparking.com2017-02-11 → 2017-02-11 · 4 obs
○ 2016-06-24 08:14:32
● 2017-02-11 23:06:20
○ 2018-03-02 19:39:12
○ 2026-05-14 13:34:04
● 2017-02-11 23:06:20
○ 2018-03-02 19:39:12
○ 2026-05-14 13:34:04
○MXlocalhost2017-02-11 → 2017-02-11 · 4 obs
○ 2016-06-24 08:14:32
● 2017-02-11 23:06:20
○ 2018-03-02 19:39:12
○ 2026-05-14 13:34:04
● 2017-02-11 23:06:20
○ 2018-03-02 19:39:12
○ 2026-05-14 13:34:04
○MXmx.snsdy.com2016-03-06 → 2016-06-24 · 4 obs
● 2016-03-06 20:11:24
● 2016-06-24 08:14:32
○ 2017-02-11 23:06:20
○ 2026-05-14 13:34:04
● 2016-06-24 08:14:32
○ 2017-02-11 23:06:20
○ 2026-05-14 13:34:04
○A66.96.162.1442016-03-06 → 2016-06-24 · 4 obs
● 2016-03-06 20:11:24
● 2016-06-24 08:14:32
○ 2017-02-11 23:06:20
○ 2026-05-14 13:34:04
● 2016-06-24 08:14:32
○ 2017-02-11 23:06:20
○ 2026-05-14 13:34:04
○A72.52.4.1192017-02-11 → 2017-02-11 · 4 obs
○ 2016-06-24 08:14:32
● 2017-02-11 23:06:20
○ 2018-03-02 19:39:12
○ 2026-05-14 13:34:04
● 2017-02-11 23:06:20
○ 2018-03-02 19:39:12
○ 2026-05-14 13:34:04
●CNAMEa.dnsapi12.com2026-04-25 → 2026-05-14 · 2 obs
● 2026-04-25 22:53:18
● 2026-05-14 13:34:04
● 2026-05-14 13:34:04
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, a.gtld-servers.net, g.gtld-servers.net, k.gtld-servers.net... | - |
| snsdy.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 snsdy.com (unsigned zone)
⏱️ Timing
Total: 310ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns1.julydns.com, ns2.julydns.com |
| CNAME | 1 | a.dnsapi12.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
snsdy.com maps to ten IP numbers: 2606:4700:e7::3151:47a9, 2606:4700:3032::818:669e, 2606:4700:3035::1a4f:5642, 2606:4700:8ca0::3dc4:21a2, 2a06:98c1:3120::5692:61a4, 104.16.250.22, 104.17.25.173, 104.18.185.26, 104.21.224.5 and 104.21.227.134.
Other host names, for instance 531566.xyz, claudeide.net, wnsse.lol, 031803.xyz and 52safe.top share IP numbers with snsdy.com.