watchsync.com - robtex.com
watchsync.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.dyna-ns.net ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::a29f:1a5c🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1b9e🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.26.92Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.dyna-ns.net | ||||||
| A | 162.159.27.158Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns1.dyna-ns.net | ||||||
| NS | ns2.dyna-ns.net ⚠️ Not in zone NS records | ||||||
| A | 2400:cb00:2049:1::a29f:1805🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 2400:cb00:2049:1::a29f:1905🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street | ||||||
| A | 162.159.24.5Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.dyna-ns.net | ||||||
| A | 162.159.25.5Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| PTR | ns2.dyna-ns.net | ||||||
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=1774755847 | ||||||
Same first word
watchsync.com |
DNS History
14 records (2 active, 12 former)
●NSns1.dyna-ns.net2026-03-10 → 2026-03-29 · 3 obs
○ 2017-04-06 07:27:48
● 2026-03-10 20:56:50
● 2026-03-29 04:10:22
● 2026-03-10 20:56:50
● 2026-03-29 04:10:22
○NSns11.domaincontrol.com2017-04-06 → 2017-04-06 · 4 obs
○ 2016-07-12 12:18:46
● 2017-04-06 07:27:48
○ 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
● 2017-04-06 07:27:48
○ 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
○NSns12.domaincontrol.com2017-04-06 → 2017-04-06 · 4 obs
○ 2016-07-12 12:18:46
● 2017-04-06 07:27:48
○ 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
● 2017-04-06 07:27:48
○ 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
●NSns2.dyna-ns.net2026-03-10 → 2026-03-29 · 3 obs
○ 2017-04-06 07:27:48
● 2026-03-10 20:56:50
● 2026-03-29 04:10:22
● 2026-03-10 20:56:50
● 2026-03-29 04:10:22
○NSns33.domaincontrol.com2015-07-23 → 2016-07-12 · 4 obs
● 2015-07-23 10:35:04
● 2016-07-12 12:18:46
○ 2017-04-06 07:27:48
○ 2026-03-29 04:10:22
● 2016-07-12 12:18:46
○ 2017-04-06 07:27:48
○ 2026-03-29 04:10:22
○NSns34.domaincontrol.com2015-07-23 → 2016-07-12 · 4 obs
● 2015-07-23 10:35:04
● 2016-07-12 12:18:46
○ 2017-04-06 07:27:48
○ 2026-03-29 04:10:22
● 2016-07-12 12:18:46
○ 2017-04-06 07:27:48
○ 2026-03-29 04:10:22
○MXmail.watchsync.com2017-04-06 → 2017-04-06 · 4 obs
○ 2016-07-12 12:18:46
● 2017-04-06 07:27:48
○ 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
● 2017-04-06 07:27:48
○ 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
○MXmailstore1.secureserver.net2015-07-23 → 2016-07-12 · 4 obs
● 2015-07-23 10:35:04
● 2016-07-12 12:18:46
○ 2017-04-06 07:27:48
○ 2026-03-29 04:10:22
● 2016-07-12 12:18:46
○ 2017-04-06 07:27:48
○ 2026-03-29 04:10:22
○MXsmtp.secureserver.net2015-07-23 → 2016-07-12 · 4 obs
● 2015-07-23 10:35:04
● 2016-07-12 12:18:46
○ 2017-04-06 07:27:48
○ 2026-03-29 04:10:22
● 2016-07-12 12:18:46
○ 2017-04-06 07:27:48
○ 2026-03-29 04:10:22
○A166.62.6.512017-04-06 → 2017-04-06 · 4 obs
○ 2016-07-12 12:18:46
● 2017-04-06 07:27:48
○ 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
● 2017-04-06 07:27:48
○ 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
○A173.230.153.512015-07-23 → 2016-07-12 · 4 obs
● 2015-07-23 10:35:04
● 2016-07-12 12:18:46
○ 2017-04-06 07:27:48
○ 2026-03-29 04:10:22
● 2016-07-12 12:18:46
○ 2017-04-06 07:27:48
○ 2026-03-29 04:10:22
○A43.110.47.2472026-03-10 → 2026-03-29 · 2 obs
○ 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
○ 2026-03-29 04:10:22
○A43.110.47.2492026-03-10 → 2026-03-29 · 2 obs
○ 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
○ 2026-03-29 04:10:22
○A54.215.31.1132026-03-10 → 2026-03-10 · 3 obs
○ 2017-04-06 07:27:48
● 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
● 2026-03-10 20:56:50
○ 2026-03-29 04:10:22
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| watchsync.com | ns2.dyna-ns.net, ns1.dyna-ns.net | - |
✅ Authoritative Response
Server:162.159.26.92
NS records: ns2.dyna-ns.net, ns1.dyna-ns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for watchsync.com (unsigned zone)
⏱️ Timing
Total: 433ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
watchsync.com is delegated to two name servers: ns1.dyna-ns.net and ns2.dyna-ns.net.
watchsync.com uses the same name server setup as other domains, including famouscountries.com, domainnamedirect.com, abalt.org, tia-tanaka.blog and admanager.eu.
Host names with four IPs
ns1.dyna-ns.net points to: 2400:cb00:2049:1::a29f:1a5c, 2400:cb00:2049:1::a29f:1b9e, 162.159.26.92 and 162.159.27.158
ns2.dyna-ns.net points to: 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5