`clarosync.com`

DNSSEC	⚠️ Not signed
NS	`ns1.domainscm.com` ⚠️ Not in zone NS records
		A	201.149.88.200^{🇲🇽 MCM201.149.88.0/24}
			PTR	`service-static-149.88.200.mcm-telecom.com.mx`
NS	`ns3.domainscm.com` ⚠️ Not in zone NS records
		A	129.213.191.231^{🇺🇸 ORACLE-OCI-31898129.213.176.0/20}

`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.net`nstld@verisign-grs.com serial=1771291435

Same first word

clarosync.com

DNS History

13 records (2 active, 11 former)

○NSns-1399.awsdns-46.org2015-07-08 → 2017-01-17 · 4 obs

● 2015-07-08 01:50:30
● 2017-01-17 03:47:46
○ 2017-01-28 03:53:16
○ 2026-03-22 10:46:42

○NSns-1610.awsdns-09.co.uk2015-07-08 → 2017-01-17 · 4 obs

● 2015-07-08 01:50:30
● 2017-01-17 03:47:46
○ 2017-01-28 03:53:16
○ 2026-03-22 10:46:42

○NSns-198.awsdns-24.com2015-07-08 → 2017-01-17 · 4 obs

● 2015-07-08 01:50:30
● 2017-01-17 03:47:46
○ 2017-01-28 03:53:16
○ 2026-03-22 10:46:42

○NSns-929.awsdns-52.net2015-07-08 → 2017-01-17 · 4 obs

● 2015-07-08 01:50:30
● 2017-01-17 03:47:46
○ 2017-01-28 03:53:16
○ 2026-03-22 10:46:42

●NSns1.domainscm.com2017-01-28 → 2026-03-22 · 3 obs

○ 2017-01-17 03:47:46
● 2017-01-28 03:53:16
● 2026-03-22 10:46:42

●NSns3.domainscm.com2017-01-28 → 2026-03-22 · 3 obs

○ 2017-01-17 03:47:46
● 2017-01-28 03:53:16
● 2026-03-22 10:46:42

○MXalt1.aspmx.l.google.com2015-07-08 → 2026-02-15 · 4 obs

● 2015-07-08 01:50:30
● 2026-02-15 10:36:34
○ 2026-02-19 18:15:20
○ 2026-03-22 10:46:42

○MXalt2.aspmx.l.google.com2015-07-08 → 2026-02-15 · 4 obs

● 2015-07-08 01:50:30
● 2026-02-15 10:36:34
○ 2026-02-19 18:15:20
○ 2026-03-22 10:46:42

○MXaspmx.l.google.com2015-07-08 → 2026-02-15 · 4 obs

● 2015-07-08 01:50:30
● 2026-02-15 10:36:34
○ 2026-02-19 18:15:20
○ 2026-03-22 10:46:42

○MXaspmx2.googlemail.com2015-07-08 → 2026-02-15 · 4 obs

● 2015-07-08 01:50:30
● 2026-02-15 10:36:34
○ 2026-02-19 18:15:20
○ 2026-03-22 10:46:42

○MXaspmx3.googlemail.com2015-07-08 → 2026-02-15 · 4 obs

● 2015-07-08 01:50:30
● 2026-02-15 10:36:34
○ 2026-02-19 18:15:20
○ 2026-03-22 10:46:42

○A50.56.17.122017-01-28 → 2026-02-15 · 5 obs

○ 2017-01-17 03:47:46
● 2017-01-28 03:53:16
● 2026-02-15 10:36:34
○ 2026-02-19 18:15:20
○ 2026-03-22 10:46:42

○A54.207.28.2282015-07-08 → 2017-01-17 · 4 obs

● 2015-07-08 01:50:30
● 2017-01-17 03:47:46
○ 2017-01-28 03:53:16
○ 2026-03-22 10:46:42

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, h.gtld-servers.net...	-
clarosync.com	ns1.domainscm.com, ns3.domainscm.com	2 records

✅ Authoritative Response

Server: 201.149.88.200

NS records: ns1.domainscm.com, ns3.domainscm.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for clarosync.com (unsigned zone)

⏱️ Timing

Total: 389ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.domainscm.com, ns3.domainscm.com)

Analysis

Name Servers

clarosync.com is delegated to two name servers ns1.domainscm.com and ns3.domainscm.com.

clarosync.com shares the same name server setup as other domains, for instance broadcastersms.com, domingosanto.com, siveta.com, prontipagos.mx and gothumbsup.com.

Host names with one IP number:

ns1.domainscm.com points to 201.149.88.200

ns3.domainscm.com points to 129.213.191.231

clarosync.com - robtex.com

clarosync.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

Name Servers

`clarosync.com`

`com`