`capcalendar.click`

DNSSEC	⚠️ Not signed
A	185.176.220.35^{🇱🇻 LV-2CLOUD-ASN16185.176.220.0/24 LV-2CLOUD-220}
		PTR	`316258.2cloud.eu`
NS	`ns1.dnsowl.com` ⭐
		A	2400:cb00:2049:1::a29f:1a88^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1bad^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.136^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.173^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.dnsowl.com`
		A	2400:cb00:2049:1::a29f:1a31^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b82^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.49^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.130^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns3.dnsowl.com`
		A	2400:cb00:2049:1::a29f:1aea^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b62^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.234^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	162.159.27.98^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`ns1.dnsowl.com`hostmaster@dnsowl.com serial=1751842851

`click`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1778715214

Same first word

capcalendar.click

DNS History

4 records (4 active, 0 former)

●NSns1.dnsowl.com2026-05-06 → 2026-05-13 · 2 obs

● 2026-05-06 16:46:44
● 2026-05-13 23:58:44

●NSns2.dnsowl.com2026-05-06 → 2026-05-13 · 2 obs

● 2026-05-06 16:46:44
● 2026-05-13 23:58:44

●NSns3.dnsowl.com2026-05-06 → 2026-05-13 · 2 obs

● 2026-05-06 16:46:44
● 2026-05-13 23:58:44

●A185.176.220.352026-05-06 → 2026-05-13 · 2 obs

● 2026-05-06 16:46:44
● 2026-05-13 23:58:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
click	ns10.trs-dns.org, ns01.trs-dns.net, ns10.trs-dns.info, ns01.trs-dns.com	-
capcalendar.click	ns2.dnsowl.com, ns1.dnsowl.com, ns3.dnsowl.com	-

✅ Authoritative Response

Server:162.159.27.173

NS records: ns2.dnsowl.com, ns1.dnsowl.com, ns3.dnsowl.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for capcalendar.click (unsigned zone)

⏱️ Timing

Total: 668ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`185.176.220.35`
NS	3	`ns1.dnsowl.com, ns2.dnsowl.com...`
SOA	1	`ns1.dnsowl.com hostmaster.dnsowl.com`

Analysis

IP Addresses

capcalendar.click points to a single IP: 185.176.220.35.

Other host names, for instance dailcalendersync.click, setscheduledate.pro, daildateschedule.pro, synccalenderly.click and gtdatescheduler.pro share IP numbers with capcalendar.click.

Name Servers

capcalendar.click is delegated to three name servers: ns1.dnsowl.com, ns2.dnsowl.com and ns3.dnsowl.com.

capcalendar.click partially shares name servers with other domains; examples include ok100t.com, colohsk.top, propartsco.com, gregorysupply.com and yyshuyuan.cc.

Host names with four IP numbers:

ns1.dnsowl.com resolves to: 2400:cb00:2049:1::a29f:1a88, 2400:cb00:2049:1::a29f:1bad, 162.159.26.136 and 162.159.27.173

ns2.dnsowl.com resolves to: 2400:cb00:2049:1::a29f:1a31, 2400:cb00:2049:1::a29f:1b82, 162.159.26.49 and 162.159.27.130

ns3.dnsowl.com resolves to: 2400:cb00:2049:1::a29f:1aea, 2400:cb00:2049:1::a29f:1b62, 162.159.26.234 and 162.159.27.98

capcalendar.click - robtex.com