fetchlayer.dev - dns.ninja

🛡️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=141, name=cloudflare-ech.com
SOA	`denver.ns.cloudflare.com`dns@cloudflare.com serial=2413776436

`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

freelychat.com

techyflare.xyz

farleytech.site

relayfetch.com

techflayer.com

theflycare.com

farleytech.com

flyteacher.de

chatfreely.cn

thecarlyfe.com

freelychat.xyz

flyteacher.com

Previous names

festivus.dev

festly.dev

festo.dev

festow.dev

festry.dev

festus.dev

fesyo.dev

fet.dev

fetan.dev

fetburner.dev

fetchanddisplay.dev

fetchapi.dev

fetchapp.dev

fetchd.dev

fetchdsl.dev

fetchform.dev

fetchfund.dev

fetchgate.dev

fetchgoat.dev

fetchit.dev

Next names

fetchly.dev

fetchmd.dev

fetchos.dev

fetchpet.dev

fetchpkg.dev

fetchprm.dev

fetchprompt.dev

fetchpulse.dev

fetchski.dev

fetchy.dev

fetep.dev

fetherolf.dev

fethr.dev

fetlife.dev

feto.dev

fetro.dev

fetterly.dev

fettle.dev

DNS History

9 records (9 active, 0 former)

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

● 2026-08-20 11:23:18
● 2026-09-02 09:14:08

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

● 2026-08-20 11:23:18
● 2026-09-02 09:14:08

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

● 2026-08-20 11:23:18
● 2026-09-02 09:14:08

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

● 2026-08-20 11:23:18
● 2026-09-02 09:14:08

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

● 2026-08-20 11:23:18
● 2026-09-02 09:14:08

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

● 2026-08-20 11:23:18
● 2026-09-02 09:14:08

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

● 2026-08-20 11:23:18
● 2026-09-02 09:14:08

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

● 2026-08-20 11:23:18
● 2026-09-02 09:14:08

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

● 2026-08-20 11:23:18
● 2026-09-02 09:14:08

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:162.159.38.168

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: 586ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.204.221, 104.21.61.13`
AAAA	2	`2606:4700:3031::6815:3d0d, 2606:4700:3031::ac43:ccdd`
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.`

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, yy542.com and two other host names share IP numbers with fetchlayer.dev.

Name Servers

fetchlayer.dev uses two name servers for its delegation: denver.ns.cloudflare.com and paloma.ns.cloudflare.com.

fetchlayer.dev uses the same name servers as several other domains — among them rajithadisanayaka999.workers.dev, casaluxe.vip, mikko-koivisto.workers.dev and two more.

fetchlayer.dev shares at least some of its name servers with other domains, including kengsha.cn, mivision.co.uk, proxy24.com and two others.

These name servers are frequently paired with the name servers lily.ns.cloudflare.com, susan.ns.cloudflare.com and leif.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

Hostname denver.ns.cloudflare.com directs to 108.162.195.196, 162.159.44.196 and 172.64.35.196 along with 3 other IP addresses.

Hostname paloma.ns.cloudflare.com directs to 108.162.194.168, 162.159.38.168 and 172.64.34.168 along with 3 other IP addresses.

Mail Servers

fetchlayer.dev is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

fetchlayer.dev has at least partial mail server overlap with other domains such as sporotz.com, vainformatica.net, ruyss.be and two more.

Hostnames that resolve to 6 IP addresses:

Hostname route1.mx.cloudflare.net directs to 162.159.205.11, 162.159.205.12 and 162.159.205.13 along with 3 other IP addresses.

Hostname route2.mx.cloudflare.net directs to 162.159.205.17, 162.159.205.18 and 162.159.205.19 along with 3 other IP addresses.

Hostname route3.mx.cloudflare.net directs to 162.159.205.23, 162.159.205.24 and 162.159.205.25 along with 3 other IP addresses.