🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`layer10security.dev`

DNSSEC	⚠️ Not signed
NS	`eva.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a72^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eva.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c072^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`eva.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2072^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`eva.ns.cloudflare.com`
		A	108.162.192.114^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eva.ns.cloudflare.com`
		A	172.64.32.114^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eva.ns.cloudflare.com`
		A	173.245.58.114^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`eva.ns.cloudflare.com`
NS	`kevin.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bbf^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kevin.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1bf^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kevin.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21bf^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kevin.ns.cloudflare.com`
		A	108.162.193.191^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kevin.ns.cloudflare.com`
		A	172.64.33.191^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kevin.ns.cloudflare.com`
		A	173.245.59.191^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kevin.ns.cloudflare.com`
MX	`mx1.alias.proton.me` ⭐
		A	176.119.200.136^{🇨🇭 Proton176.119.200.0/24}
			PTR	`mx1.simplelogin.co`
			PTR	`mx2.simplelogin.co`
		A	185.205.70.136^{🇫🇷 Proton185.205.70.0/24}
			PTR	`mx1.simplelogin.co`
			PTR	`mx2.simplelogin.co`
MX	`mx2.alias.proton.me`⁽²⁰⁾
		A	176.119.200.136^{🇨🇭 Proton176.119.200.0/24}
			PTR	`mx1.simplelogin.co`
			PTR	`mx2.simplelogin.co`
		A	185.205.70.136^{🇫🇷 Proton185.205.70.0/24}
			PTR	`mx1.simplelogin.co`
			PTR	`mx2.simplelogin.co`
TXT	`google-site-verification=t3AJ5x4GrQOoPzdR2VVtWkQr0bm0PV_UwNxfvwKvNac`
TXT	`pm-verification=xfxgfoynxrxvxkniscfalicalssqds`
TXT	`v=spf1 include:alias.proton.me ~all`
SOA	`eva.ns.cloudflare.com`dns@cloudflare.com serial=2414264478

`dev`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=1

🔒 HSTS Preload (+subdomains)

Same first word

layer10security.io

layer10security.dev

Previous names

laxxifer.dev

lay.dev

lay3rlabs.dev

laya.dev

layag.dev

layana.dev

layang.dev

layar138.dev

layardrama.dev

layaremas.dev

layarkaca21.dev

layarskor.dev

layco.dev

layendan.dev

layer-7.dev

layer-cake.dev

layer.dev

layer0labs.dev

layer1-labs.dev

layer1.dev

Next names

DNS History

4 records (4 active, 0 former)

●NSeva.ns.cloudflare.com2026-09-05 → 2026-09-09 · 2 obs

● 2026-09-05 12:16:22
● 2026-09-09 12:57:00

●NSkevin.ns.cloudflare.com2026-09-05 → 2026-09-09 · 2 obs

● 2026-09-05 12:16:22
● 2026-09-09 12:57:00

●MXmx1.alias.proton.me2026-09-05 → 2026-09-09 · 2 obs

● 2026-09-05 12:16:22
● 2026-09-09 12:57:00

●MXmx2.alias.proton.me2026-09-05 → 2026-09-09 · 2 obs

● 2026-09-05 12:16:22
● 2026-09-09 12:57:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...	10 records
layer10security.dev	kevin.ns.cloudflare.com, eva.ns.cloudflare.com	-

✅ Authoritative Response

Server:173.245.59.191

NS records: kevin.ns.cloudflare.com, eva.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for layer10security.dev (unsigned zone)

⏱️ Timing

Total: 977ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`eva.ns.cloudflare.com, kevin.ns.cloudflare.com`
MX	2	`mx1.alias.proton.me (pri: 10), mx2.alias.proton.me (pri: 20)`
TXT	3	`google-site-verification=t3AJ5x4GrQOoPzd, pm-verification=xfxgfoynxrxvxkniscfalica...`
SOA	1	`eva.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)

Analysis

Name Servers

Two name servers handle the delegation for layer10security.dev: eva.ns.cloudflare.com and kevin.ns.cloudflare.com.

layer10security.dev shares its name server setup with other domains, including skorp-io.de, gayanpod.com, val1megai.workers.dev and two others.

layer10security.dev partially shares its NS delegation with several other domains, including js-6cs.pages.dev, tendepinrai1971.workers.dev, drgncabe.com and two others.

These name servers often co-occur with the name servers alberto.ns.cloudflare.com.

Host names with 6 IP numbers:

eva.ns.cloudflare.com resolves to 108.162.192.114, 172.64.32.114 and 173.245.58.114 among others, with 3 other IP addresses in total.

kevin.ns.cloudflare.com resolves to 108.162.193.191, 172.64.33.191 and 173.245.59.191 among others, with 3 other IP addresses in total.

Mail Servers

layer10security.dev has two mail servers: mx1.alias.proton.me and mx2.alias.proton.me.

layer10security.dev shares the same mail server setup as other domains, including juuso.eu, facelook.nl, janeanlwatkins.com and two others.

layer10security.dev shares mail servers — at least in part — with other domains, including love2bbq.nl, runesmite.com, boursicot.fr and two others.

The mail servers mail.protonmail.ch and mailsec.protonmail.ch regularly co-occur with these mail servers.

mx1.alias.proton.me and mx2.alias.proton.me each point to two IP numbers — 176.119.200.136 and 185.205.70.136 — making both hosts identical in their DNS resolution.

mx1.alias.proton.me along with mx2.alias.proton.me each resolve to 176.119.200.136 IP addresses.

mx1.alias.proton.me along with mx2.alias.proton.me each resolve to 185.205.70.136 IP addresses.

layer10security.dev - robtex.com