🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`nextlayersec.dev`

DNSSEC	🔒 Signed (DS record present)
A	2606:4700:3030::6815:47a^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::ac43:8411^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.4.122^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.132.17^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`courtney.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:2682^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`courtney.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c282^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`courtney.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2282^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`courtney.ns.cloudflare.com`
		A	108.162.194.130^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`courtney.ns.cloudflare.com`
		A	162.159.38.130^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`courtney.ns.cloudflare.com`
		A	172.64.34.130^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`courtney.ns.cloudflare.com`
NS	`elmo.ns.cloudflare.com`
		A	2606:4700:58::adf5:3ba3^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elmo.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1a3^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`elmo.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21a3^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`elmo.ns.cloudflare.com`
		A	108.162.193.163^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elmo.ns.cloudflare.com`
		A	172.64.33.163^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elmo.ns.cloudflare.com`
		A	173.245.59.163^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`elmo.ns.cloudflare.com`
MX	`nextlayersec-dev.l-v1.mx.microsoft` ⭐
		A	2a01:111:f403:c918::5^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-byapr05cu00805.inbound.protection.outlook.com`
		A	2a01:111:f403:c931::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sa9pr03cu00201.inbound.protection.outlook.com`
		A	2a01:111:f403:f90d::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr0501cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:f913::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-cy1pr03cu00100.inbound.protection.outlook.com`
		A	52.101.8.34^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-dm2pr04cu00102.inbound.protection.outlook.com`
		A	52.101.9.0^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl2pr02cu00100.inbound.protection.outlook.com`
		A	52.101.40.24^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy5pr05cu00100.inbound.protection.outlook.com`
		A	52.101.50.13^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mw2pr02cu00605.inbound.protection.outlook.com`
TXT	`MS=ms83511414`
TXT	`MS=ms84837792`
TXT	`amazon-business-verification=5e29b239f8adf42b07c99a36cbe7c2697c9ab4f271dc0550...`
TXT	`nextlayersec.dev`
TXT	`openai-domain-verification=dv-VgyUg3OJxbZws1ffGBlqbFRs`
TXT	`slack-domain-verification=stAIpZXW5mWG8KuQARXfbI01eNzvCHIylWJnbnCE`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.4.122, 172.67.132.17
		IPv6 hints	2606:4700:3030::6815:47a, 2606:4700:3034::ac43:8411
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=144, name=cloudflare-ech.com
SOA	`courtney.ns.cloudflare.com`dns@cloudflare.com serial=2413298171

`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

nextlayersec.dev

nextlayersec.io

Previous names

Next names

DNS History

7 records (7 active, 0 former)

●NScourtney.ns.cloudflare.com2026-08-26 → 2026-09-01 · 2 obs

● 2026-08-26 18:48:02
● 2026-09-01 13:13:56

●NSelmo.ns.cloudflare.com2026-08-26 → 2026-09-01 · 2 obs

● 2026-08-26 18:48:02
● 2026-09-01 13:13:56

●MXnextlayersec-dev.l-v1.mx.microsoft2026-08-26 → 2026-09-01 · 2 obs

● 2026-08-26 18:48:02
● 2026-09-01 13:13:56

●A104.21.4.1222026-08-26 → 2026-09-01 · 2 obs

● 2026-08-26 18:48:02
● 2026-09-01 13:13:56

●A172.67.132.172026-08-26 → 2026-09-01 · 2 obs

● 2026-08-26 18:48:02
● 2026-09-01 13:13:56

●A2606:4700:3030::6815:47a2026-08-26 → 2026-09-01 · 2 obs

● 2026-08-26 18:48:02
● 2026-09-01 13:13:56

●A2606:4700:3034::ac43:84112026-08-26 → 2026-09-01 · 2 obs

● 2026-08-26 18:48:02
● 2026-09-01 13:13:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld3.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com...	-
nextlayersec.dev	courtney.ns.cloudflare.com, elmo.ns.cloudflare.com	-

✅ Authoritative Response

Server:162.159.38.130

NS records: courtney.ns.cloudflare.com, elmo.ns.cloudflare.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 823ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.4.122, 172.67.132.17`
AAAA	2	`2606:4700:3034::ac43:8411, 2606:4700:3030::6815:47a`
NS	2	`courtney.ns.cloudflare.com, elmo.ns.cloudflare.com`
MX	1	`nextlayersec-dev.l-v1.mx.microsoft (pri:`
TXT	7	`MS=ms83511414, MS=ms84837792...`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`courtney.ns.cloudflare.com dns.cloudflar`

Analysis

IP Addresses

nextlayersec.dev directs to four IP numbers, which are 104.21.4.122, 172.67.132.17, 2606:4700:3030::6815:47a and 2606:4700:3034::ac43:8411.

Among the host names that share IP numbers with nextlayersec.dev are stockter.info, aarobetulima.xyz, megacondensed.club and two others.

Name Servers

nextlayersec.dev is delegated to two name servers: courtney.ns.cloudflare.com and elmo.ns.cloudflare.com.

nextlayersec.dev has the same name server delegation as a number of other domains, such as badea-masoud.workers.dev, navaei.workers.dev, gezenyudistira6.workers.dev and two more.

There is at least partial name server overlap between nextlayersec.dev and other domains — underpaidgenius.com, sh00trs-tv.workers.dev, djtrucks.nl and two more among them.

These name servers are routinely deployed together with the name servers karl.ns.cloudflare.com.

Host names resolving to 6 IP numbers:

courtney.ns.cloudflare.com resolves to 108.162.194.130, 162.159.38.130, 172.64.34.130 and 3 other IP addresses.

elmo.ns.cloudflare.com resolves to 108.162.193.163, 172.64.33.163, 173.245.59.163 and 3 other IP addresses.

Mail Servers

nextlayersec.dev routes its mail through a single mail server, nextlayersec-dev.l-v1.mx.microsoft.

nextlayersec-dev.l-v1.mx.microsoft directs to 8 IP numbers, including 52.101.8.34, 52.101.9.0 and 52.101.40.24, along with 5 other.

nextlayersec.dev - robtex.com