🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`iforge.dev`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:ad1^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3031::ac43:a484^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.10.209^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.164.132^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`donald.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b9e^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`donald.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c19e^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`donald.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:219e^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`donald.ns.cloudflare.com`
		A	108.162.193.158^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`donald.ns.cloudflare.com`
		A	172.64.33.158^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`donald.ns.cloudflare.com`
		A	173.245.59.158^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`donald.ns.cloudflare.com`
NS	`tegan.ns.cloudflare.com`
		A	2606:4700:50::adf5:3ae2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tegan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0e2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`tegan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20e2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`tegan.ns.cloudflare.com`
		A	108.162.192.226^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tegan.ns.cloudflare.com`
		A	172.64.32.226^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tegan.ns.cloudflare.com`
		A	173.245.58.226^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tegan.ns.cloudflare.com`
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`
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	`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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.10.209, 172.67.164.132
		IPv6 hints	2606:4700:3031::6815:ad1, 2606:4700:3031::ac43:a484
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=105, name=cloudflare-ech.com
SOA	`donald.ns.cloudflare.com`dns@cloudflare.com serial=2419702987

`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

iforge.uk

iforge.se

iforge.ca

iforge.io

iforge.site

iforge.eu

iforge.xyz

iforge.duckdns.org

iforge.page

iforge.org

iforge.us

iforge.tech

iforge.ai

iforge.dev

iforge.net

iforge.pl

iforge.online

iforge.co.in

iforge.in

iforge.ir

iforge.cn

iforge.it

iforge.si

iforge.group

iforge.com

iforge.co

iforge.cc

iforge.me

iforge.de

iforge.tv

iforge.app

iforge.com.cn

iforge.com.br

iforge.tools

iforge.co.uk

Similar names

fregio.mk

firego.cz

foiger.asia

reifgo.com

gferoi.ph

forgie.uk

figero.ca

frogie.space

ferigo.fr

ferigo.net

forgei.biz

gofire.ca

gofire.money

forgie.nl

firego.com.mx

firego.org

rigfoe.rest

gofire.co.uk

grefio.de

fregio.ru

fergio.uk

figero.se

frigeo.com.br

goefir.cn

ferogi.cn

grefio.se

freigo.pages.dev

goefir.com

frogie.com

grefio.ro

freigo.com

gofrei.de

grofie.com

gofire.eu

gefrio.com

goferi.xyz

forgie.net.ph

erogif.ru

gofire.zeabur.app

forgie.ca

gorife.cn

frogie.org

grefio.pl

forgie.workers.dev

ferigo.eu

gifero.com

grifeo.it

gofire.app

refigo.lat

freigo.app

ogfire.com

forgie.art

gofrei.pages.dev

giofer.com

goefir.ru

freigo.jp

firego.net

girefo.cn

gifero.cn

figore.com.tr

frogie.app

efrigo.cz

frigeo.at

fregio.ro

grofie.hu

gofire.vip

ferigo.de

efrigo.com.my

figero.io

gofire.today

frigeo.de

firego.pro

firego.ru

firego.com

giofre.it

ifergo.com

goferi.no

fergio.by

ergofi.com

erogif.work

gifore.com

fregio.gr

fegiro.com

foregi.cn

refigo.lt

gorefi.ca

gefroi.de

Previous names

ifloom.dev

iflow.dev

iflr.dev

ifly.dev

iflynyx.dev

ifmapp.dev

ifms.dev

ifndef.dev

ifnews.dev

ifnil.dev

ifnull.dev

ifo.dev

ifold.dev

ifone.dev

ifonts.dev

ifoodx.dev

ifor.dev

iforce.dev

iforevents.dev

Next names

iforgot.dev

iformas.dev

iforth.dev

iforum.dev

ifost.dev

ifoundu.dev

ifp.dev

ifpt.dev

ifqy.dev

ifrah.dev

ifraheem.dev

ifrahim.dev

ifralou.dev

iframe-ly.dev

iframe.dev

iframely.dev

iframetest.dev

iframetester.dev

ifredsantos.dev

ifree.dev

DNS History

9 records (9 active, 0 former)

●NSdonald.ns.cloudflare.com2026-09-12 → 2026-11-09 · 2 obs

● 2026-09-12 01:00:16
● 2026-11-09 19:44:12

●NStegan.ns.cloudflare.com2026-09-12 → 2026-11-09 · 2 obs

● 2026-09-12 01:00:16
● 2026-11-09 19:44:12

●MXroute1.mx.cloudflare.net2026-09-12 → 2026-11-09 · 2 obs

● 2026-09-12 01:00:16
● 2026-11-09 19:44:12

●MXroute2.mx.cloudflare.net2026-09-12 → 2026-11-09 · 2 obs

● 2026-09-12 01:00:16
● 2026-11-09 19:44:12

●MXroute3.mx.cloudflare.net2026-09-12 → 2026-11-09 · 2 obs

● 2026-09-12 01:00:16
● 2026-11-09 19:44:12

●A104.21.10.2092026-11-08 → 2026-11-09 · 2 obs

● 2026-11-08 04:47:52
● 2026-11-09 19:44:12

●A172.67.164.1322026-11-08 → 2026-11-09 · 2 obs

● 2026-11-08 04:47:52
● 2026-11-09 19:44:12

●A2606:4700:3031::6815:ad12026-11-08 → 2026-11-09 · 2 obs

● 2026-11-08 04:47:52
● 2026-11-09 19:44:12

●A2606:4700:3031::ac43:a4842026-11-08 → 2026-11-09 · 2 obs

● 2026-11-08 04:47:52
● 2026-11-09 19:44:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...	-
iforge.dev	tegan.ns.cloudflare.com, donald.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.33.158

NS records: tegan.ns.cloudflare.com, donald.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for iforge.dev (unsigned zone)

⏱️ Timing

Total: 821ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.164.132, 104.21.10.209`
AAAA	2	`2606:4700:3031::ac43:a484, 2606:4700:3031::6815:ad1`
NS	2	`donald.ns.cloudflare.com, tegan.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 21), route2.mx.cloudflare.net (pri: 49)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`donald.ns.cloudflare.com dns.cloudflare.`

Analysis

IP Addresses

iforge.dev directs to four IP numbers, which are 104.21.10.209, 172.67.164.132, 2606:4700:3031::6815:ad1 and 2606:4700:3031::ac43:a484.

Among the host names that share IP numbers with iforge.dev are ebupeho.top, ichschick.com, writing.fr and two others.

Name Servers

iforge.dev uses two name servers for its delegation: donald.ns.cloudflare.com and tegan.ns.cloudflare.com.

iforge.dev has the same name server delegation as a number of other domains, such as photobatl2759741546.pages.dev, autumn-dew-f182.workers.dev, vickeynotari7q4f9.pages.dev and two more.

There is at least partial name server overlap between iforge.dev and other domains — marsbahisgloball.com, morgan-roofing.pages.dev, corexnexusnetw-ork.sbs and two more among them.

The name servers mustafa.ns.cloudflare.com, magnolia.ns.cloudflare.com and daphne.ns.cloudflare.com are often found in combination with these name servers.

Host names resolving to 6 IP numbers:

Hostname donald.ns.cloudflare.com directs to 108.162.193.158, 172.64.33.158 and 173.245.59.158 along with 3 other IP addresses.

Hostname tegan.ns.cloudflare.com directs to 108.162.192.226, 172.64.32.226 and 173.245.58.226 along with 3 other IP addresses.

Mail Servers

Incoming mail for iforge.dev is delivered via three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

iforge.dev shares at least some of its mail servers with other domains — for example spinogambinode.com, sproutingtech.org, warriorlegend.biz.id and two more.

Host names resolving to 6 IP numbers:

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.

iforge.dev - robtex.com

iforge.dev

dev

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`iforge.dev`

`dev`