🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`fetchlayer.dev`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:3d0d^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3031::ac43:ccdd^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.61.13^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.204.221^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`denver.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2cc4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3c4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`denver.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23c4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`denver.ns.cloudflare.com`
		A	108.162.195.196^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
		A	162.159.44.196^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
		A	172.64.35.196^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`denver.ns.cloudflare.com`
NS	`paloma.ns.cloudflare.com`
		A	2606:4700:50::a29f:26a8^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paloma.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2a8^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`paloma.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22a8^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`paloma.ns.cloudflare.com`
		A	108.162.194.168^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paloma.ns.cloudflare.com`
		A	162.159.38.168^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paloma.ns.cloudflare.com`
		A	172.64.34.168^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`paloma.ns.cloudflare.com`
MX	`route3.mx.cloudflare.net` ⭐
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁴⁴⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽⁸⁸⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
TXT	`google-site-verification=e02B1o_XGfG7vHHl-tbmbgtttDaBjoDlFuPT_GxIhAE`
TXT	`google-site-verification=vN8ddqqRp3JchPgXpSNKDAydSE5NEfOmc1oGt4SAdh8`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.61.13, 172.67.204.221
		IPv6 hints	2606:4700:3031::6815:3d0d, 2606:4700:3031::ac43:ccdd
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=7, name=cloudflare-ech.com
SOA	`denver.ns.cloudflare.com`dns@cloudflare.com serial=2412488457

`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

fetchlayer.dev

fetchlayer.xyz

Similar names

techyflare.xyz

farleytech.site

techflayer.com

theflycare.com

flyteacher.de

thecarlyfe.com

Previous names

ferrumcode.dev

fersan.dev

ferthomas.dev

fes-.dev

fes-frankfurt.dev

fes-tut.dev

fes.dev

fesari.dev

feser-graf.dev

fespli.dev

fessior.dev

festi.dev

festivus.dev

festly.dev

festo.dev

festry.dev

fesyo.dev

fetchapp.dev

fetchgoat.dev

fetchit.dev

Next names

DNS History

9 records (9 active, 0 former)

●NSdenver.ns.cloudflare.com2026-08-20 → 2026-08-24 · 2 obs

● 2026-08-20 11:23:18
● 2026-08-24 13:43:32

●NSpaloma.ns.cloudflare.com2026-08-20 → 2026-08-24 · 2 obs

● 2026-08-20 11:23:18
● 2026-08-24 13:43:32

●MXroute1.mx.cloudflare.net2026-08-20 → 2026-08-24 · 2 obs

● 2026-08-20 11:23:18
● 2026-08-24 13:43:32

●MXroute2.mx.cloudflare.net2026-08-20 → 2026-08-24 · 2 obs

● 2026-08-20 11:23:18
● 2026-08-24 13:43:32

●MXroute3.mx.cloudflare.net2026-08-20 → 2026-08-24 · 2 obs

● 2026-08-20 11:23:18
● 2026-08-24 13:43:32

●A104.21.61.132026-08-20 → 2026-08-24 · 2 obs

● 2026-08-20 11:23:18
● 2026-08-24 13:43:32

●A172.67.204.2212026-08-20 → 2026-08-24 · 2 obs

● 2026-08-20 11:23:18
● 2026-08-24 13:43:32

●A2606:4700:3031::6815:3d0d2026-08-20 → 2026-08-24 · 2 obs

● 2026-08-20 11:23:18
● 2026-08-24 13:43:32

●A2606:4700:3031::ac43:ccdd2026-08-20 → 2026-08-24 · 2 obs

● 2026-08-20 11:23:18
● 2026-08-24 13:43:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	10 records
fetchlayer.dev	paloma.ns.cloudflare.com, denver.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.195.196

NS records: paloma.ns.cloudflare.com, denver.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fetchlayer.dev (unsigned zone)

⏱️ Timing

Total: 589ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.204.221, 104.21.61.13`
AAAA	2	`2606:4700:3031::ac43:ccdd, 2606:4700:3031::6815:3d0d`
NS	2	`denver.ns.cloudflare.com, paloma.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 38), route2.mx.cloudflare.net (pri: 44)...`
TXT	3	`google-site-verification=e02B1o_XGfG7vHH, google-site-verification=vN8ddqqRp3JchPg...`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`denver.ns.cloudflare.com dns.cloudflare.`

📌 Glue Records Collected

Total: 10

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

Analysis

IP Addresses

fetchlayer.dev resolves to four IP addresses: 104.21.61.13, 172.67.204.221, 2606:4700:3031::6815:3d0d and 2606:4700:3031::ac43:ccdd.

antivpn.io, ee.spreee.pro, stmpecasparatratores.com.br plus two other host names have IP numbers in common with fetchlayer.dev.

Name Servers

Two name servers handle the delegation for fetchlayer.dev: denver.ns.cloudflare.com and paloma.ns.cloudflare.com.

The name server configuration of fetchlayer.dev is shared with other domains, for instance casaluxe.vip, babaminerals.in, n8ntunnel.xyz and two others.

fetchlayer.dev has at least partial name server overlap with other domains, such as kengsha.cn, mivision.co.uk, proxy24.com and two others.

These name servers tend to appear together with the name servers jill.ns.cloudflare.com, susan.ns.cloudflare.com and lily.ns.cloudflare.com.

Hosts with 6 IP addresses each:

denver.ns.cloudflare.com resolves to 108.162.195.196, 162.159.44.196 and 172.64.35.196 among others, with 3 other IP addresses in total.

paloma.ns.cloudflare.com resolves to 108.162.194.168, 162.159.38.168 and 172.64.34.168 among others, with 3 other IP addresses in total.

Mail Servers

fetchlayer.dev has three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

At least some of the mail servers used by fetchlayer.dev are shared with other domains: sporotz.com, vainformatica.net, ruyss.be and two others among them.

Hosts with 6 IP addresses each:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12 and 162.159.205.13 among others, with 3 other IP addresses in total.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18 and 162.159.205.19 among others, with 3 other IP addresses in total.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24 and 162.159.205.25 among others, with 3 other IP addresses in total.

fetchlayer.dev - robtex.com

fetchlayer.dev

dev

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`fetchlayer.dev`

`dev`