`earlockly.click`

DNSSEC	⚠️ Not signed
NS	`fatima.ns.cloudflare.com` ⚠️ Not in zone NS records
		A	2606:4700:50::a29f:26bc^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fatima.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2bc^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`fatima.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22bc^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`fatima.ns.cloudflare.com`
		A	108.162.194.188^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fatima.ns.cloudflare.com`
		A	162.159.38.188^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fatima.ns.cloudflare.com`
		A	172.64.34.188^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`fatima.ns.cloudflare.com`
NS	`pedro.ns.cloudflare.com` ⚠️ Not in zone NS records
		A	2606:4700:58::a29f:2cb7^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pedro.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3b7^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`pedro.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23b7^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`pedro.ns.cloudflare.com`
		A	108.162.195.183^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pedro.ns.cloudflare.com`
		A	162.159.44.183^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pedro.ns.cloudflare.com`
		A	172.64.35.183^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pedro.ns.cloudflare.com`

`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=1785588642

⚠️ On DNS blocklist: tif

Same first word

earlockly.click

Similar names

locklayer.co.uk

cloakerly.com

DNS History

4 records (2 active, 2 former)

●NSfatima.ns.cloudflare.com2026-07-24 → 2026-08-01 · 2 obs

● 2026-07-24 23:57:08
● 2026-08-01 12:56:32

●NSpedro.ns.cloudflare.com2026-07-24 → 2026-08-01 · 2 obs

● 2026-07-24 23:57:08
● 2026-08-01 12:56:32

○A2a02:4780:41:db43::12026-07-24 → 2026-07-24 · 2 obs

● 2026-07-24 23:57:08
○ 2026-08-01 12:56:32

○A72.60.182.1312026-07-24 → 2026-07-24 · 2 obs

● 2026-07-24 23:57:08
○ 2026-08-01 12:56:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
click	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	-
earlockly.click	pedro.ns.cloudflare.com, fatima.ns.cloudflare.com	-

✅ Authoritative Response

Server:162.159.38.188

NS records: pedro.ns.cloudflare.com, fatima.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for earlockly.click (unsigned zone)

⏱️ Timing

Total: 153ms | Queries: -

📄 Records

Type	Count	Sample Data

Analysis

Name Servers

Two name servers handle the delegation for earlockly.click: fatima.ns.cloudflare.com and pedro.ns.cloudflare.com.

earlockly.click uses the same name servers as several other domains — among them narixavapartners.digital, relitdata.digital, pacativelayer.click and two more.

At least some of earlockly.click's name servers are shared with other domains, for example privacymonster.co, webstandard.dk, 5ip.eu and two more.

These name servers tend to be used in conjunction with the name servers fred.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

fatima.ns.cloudflare.com resolves to 108.162.194.188, 162.159.38.188 and 172.64.34.188 among others, with 3 other IP addresses in total.

pedro.ns.cloudflare.com resolves to 108.162.195.183, 162.159.44.183 and 172.64.35.183 among others, with 3 other IP addresses in total.

earlockly.click - robtex.com

earlockly.click

click