🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`voidkey.cloud`

DNSSEC	⚠️ Not signed
NS	`coco.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a68^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`coco.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c068^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`coco.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2068^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`coco.ns.cloudflare.com`
		A	108.162.192.104^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`coco.ns.cloudflare.com`
		A	172.64.32.104^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`coco.ns.cloudflare.com`
		A	173.245.58.104^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`coco.ns.cloudflare.com`
NS	`steven.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c11^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`steven.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c311^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`steven.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2311^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`steven.ns.cloudflare.com`
		A	108.162.195.17^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`steven.ns.cloudflare.com`
		A	162.159.44.17^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`steven.ns.cloudflare.com`
		A	172.64.35.17^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`steven.ns.cloudflare.com`
SOA	`coco.ns.cloudflare.com`dns@cloudflare.com serial=2415192671

`cloud`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1790876128

Same first word

voidkey.net

voidkey.cloud

voidkey.ru

voidkey.io

voidkey.se

voidkey.stream

voidkey.shop

voidkey.com

voidkey.dev

voidkey.dk

Similar names

Previous names

Next names

DNS History

2 records (2 active, 0 former)

●NScoco.ns.cloudflare.com2026-09-18 → 2026-10-01 · 2 obs

● 2026-09-18 05:42:54
● 2026-10-01 18:27:20

●NSsteven.ns.cloudflare.com2026-09-18 → 2026-10-01 · 2 obs

● 2026-09-18 05:42:54
● 2026-10-01 18:27:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cloud	ns10.trs-dns.org, ns01.trs-dns.net, ns01.trs-dns.com, ns10.trs-dns.info	-
voidkey.cloud	coco.ns.cloudflare.com, steven.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.35.17

NS records: coco.ns.cloudflare.com, steven.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for voidkey.cloud (unsigned zone)

⏱️ Timing

Total: 635ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`coco.ns.cloudflare.com, steven.ns.cloudflare.com`
SOA	1	`coco.ns.cloudflare.com dns.cloudflare.co`

Analysis

Name Servers

DNS delegation for voidkey.cloud points to two name servers: coco.ns.cloudflare.com and steven.ns.cloudflare.com.

The name server configuration of voidkey.cloud is shared with other domains, for instance imsangbeom.workers.dev, shcontrol.work, formtech.dev and two others.

There is at least partial name server overlap between voidkey.cloud and other domains — ikonfishing.com, c4244784a291.com, gsowners.com and two more among them.

These name servers frequently co-occur with the name servers rose.ns.cloudflare.com and ruben.ns.cloudflare.com.

Hosts with 6 IP addresses each:

coco.ns.cloudflare.com has IP addresses 108.162.192.104, 172.64.32.104 and 173.245.58.104, plus 3 other.

steven.ns.cloudflare.com has IP addresses 108.162.195.17, 162.159.44.17 and 172.64.35.17, plus 3 other.

voidkey.cloud - robtex.com

voidkey.cloud

cloud