voidbringer.dev - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`voidbringer.dev`

DNSSEC	⚠️ Not signed
A	2606:4700:3036::6815:4f46^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:a936^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.79.70^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.169.54^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`chris.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b55^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chris.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c155^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`chris.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2155^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`chris.ns.cloudflare.com`
		A	108.162.193.85^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chris.ns.cloudflare.com`
		A	172.64.33.85^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chris.ns.cloudflare.com`
		A	173.245.59.85^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chris.ns.cloudflare.com`
NS	`ines.ns.cloudflare.com`
		A	2606:4700:50::adf5:3aa4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ines.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0a4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ines.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20a4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ines.ns.cloudflare.com`
		A	108.162.192.164^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ines.ns.cloudflare.com`
		A	172.64.32.164^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ines.ns.cloudflare.com`
		A	173.245.58.164^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ines.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	`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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.79.70, 172.67.169.54
		IPv6 hints	2606:4700:3036::6815:4f46, 2606:4700:3037::ac43:a936
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=86, name=cloudflare-ech.com
SOA	`chris.ns.cloudflare.com`dns@cloudflare.com serial=2414423926

`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

voidbringer.workers.dev

voidbringer.duckdns.org

voidbringer.dev

voidbringer.de

Similar names

brivonridge.com

Previous names

void0.dev

void0ai.dev

void101.dev

void2.dev

void2610.dev

void3.dev

void8.dev

voidable.dev

voidaep.dev

voidagent.dev

voidalttab.dev

voidance.dev

voidangel.dev

voidawake.dev

voidbarbxe.dev

voidbear.dev

voidbit.dev

voidblock.dev

voidbloom.dev

voidbox.dev

Next names

DNS History

9 records (9 active, 0 former)

●NSchris.ns.cloudflare.com2026-09-11 → 2026-09-15 · 2 obs

● 2026-09-11 07:20:12
● 2026-09-15 01:24:42

●NSines.ns.cloudflare.com2026-09-11 → 2026-09-15 · 2 obs

● 2026-09-11 07:20:12
● 2026-09-15 01:24:42

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

● 2026-09-11 07:20:12
● 2026-09-15 01:24:42

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

● 2026-09-11 07:20:12
● 2026-09-15 01:24:42

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

● 2026-09-11 07:20:12
● 2026-09-15 01:24:42

●A104.21.79.702026-09-11 → 2026-09-15 · 2 obs

● 2026-09-11 07:20:12
● 2026-09-15 01:24:42

●A172.67.169.542026-09-11 → 2026-09-15 · 2 obs

● 2026-09-11 07:20:12
● 2026-09-15 01:24:42

●A2606:4700:3036::6815:4f462026-09-11 → 2026-09-15 · 2 obs

● 2026-09-11 07:20:12
● 2026-09-15 01:24:42

●A2606:4700:3037::ac43:a9362026-09-11 → 2026-09-15 · 2 obs

● 2026-09-11 07:20:12
● 2026-09-15 01:24:42

🔍 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
voidbringer.dev	ines.ns.cloudflare.com, chris.ns.cloudflare.com	-

✅ Authoritative Response

Server:173.245.58.164

NS records: ines.ns.cloudflare.com, chris.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for voidbringer.dev (unsigned zone)

⏱️ Timing

Total: 2008ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.169.54, 104.21.79.70`
AAAA	2	`2606:4700:3037::ac43:a936, 2606:4700:3036::6815:4f46`
NS	2	`chris.ns.cloudflare.com, ines.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 61), route3.mx.cloudflare.net (pri: 86)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`chris.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 10

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

Analysis

IP Addresses

voidbringer.dev points to the four IP addresses 104.21.79.70, 172.67.169.54, 2606:4700:3036::6815:4f46 and 2606:4700:3037::ac43:a936.

elizabethjuddllc.com, arzamas.org, areowifi.net and two other host names share IP numbers with voidbringer.dev.

Name Servers

voidbringer.dev is delegated to two name servers: chris.ns.cloudflare.com and ines.ns.cloudflare.com.

voidbringer.dev uses the same name servers as several other domains — among them nookaround.com, rtb-house.store, tisa311124.workers.dev and two more.

The name servers of voidbringer.dev overlap at least partially with those of other domains — among them tyuucvnmbnvbcx.pages.dev, onosfactory.pages.dev, funclub888.online and two more.

It is common to find these name servers alongside the name servers quincy.ns.cloudflare.com, laura.ns.cloudflare.com, elliot.ns.cloudflare.com and two others.

Hostnames that resolve to 6 IP addresses:

chris.ns.cloudflare.com resolves to 108.162.193.85, 172.64.33.85, 173.245.59.85 and 3 other IP addresses.

ines.ns.cloudflare.com resolves to 108.162.192.164, 172.64.32.164, 173.245.58.164 and 3 other IP addresses.

Mail Servers

Mail for voidbringer.dev is routed through three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

voidbringer.dev has at least partial mail server overlap with other domains such as killblue.store, vhsfilter.com, pickleseeds.com and two more.

Hostnames that resolve to 6 IP addresses:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12, 162.159.205.13 and 3 other IP addresses.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18, 162.159.205.19 and 3 other IP addresses.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24, 162.159.205.25 and 3 other IP addresses.