`voidworks.co`

DNSSEC	⚠️ Not signed
A	198.202.211.1^{🇺🇸 CLOUDFLARESPECTRUM198.202.211.0/24 Webflow}
NS	`pdns1.registrar-servers.com` ⭐
		A	2610:a1:1024::100^{🇺🇸 MAINT-ID-120082610:a1:1024::/48 Neustar}
		A	156.154.132.100^{🇺🇸 MAINT-ID-12008156.154.132.0/24 Neustar}
NS	`pdns2.registrar-servers.com`
		A	2610:a1:1025::100^{🇺🇸 MAINT-ID-120082610:a1:1025::/48 Neustar}
		A	156.154.133.100^{🇺🇸 MAINT-ID-12008156.154.133.0/24 Neustar}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4023:c03::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`dy-in-f26.1e100.net`
		A	142.251.2.26^{🇺🇸 Google142.251.2.0/24}
			PTR	`dl-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:2801::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausi-in-f26.1e100.net`
		A	192.178.128.27^{🇺🇸 Google192.178.128.0/24}
			PTR	`lcausi-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:1015::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f27.1e100.net`
		A	172.253.135.26^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2607:f8b0:4023:2801::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausi-in-f26.1e100.net`
		A	192.178.128.26^{🇺🇸 Google192.178.128.0/24}
			PTR	`lcausi-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2607:f8b0:4023:1015::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f26.1e100.net`
		A	172.253.135.26^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f26.1e100.net`
TXT	`v=spf1 include:servers.mcsv.net ?all`
TXT	`MS=7F3B3B426D77AF5919E924173D9FC61DD9777254`
TXT	`facebook-domain-verification=1478gg9a4228xvwktva2323c1yrhl3`
TXT	`google-site-verification=Nr_zzASnOpTapxEbeGWgITL0eg-YqSAlZKid3A4NsJ4`
TXT	`google-site-verification=_IYOq4majOOwXtCYHO778FkkP8Kw5IWY_ikWkKSggBM`
SOA	`pdns1.registrar-servers.com`hostmaster@registrar-servers.com serial=1762322214

`co`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns0.centralnic.net` ⭐
	NS	`a.registrydns.co`
	NS	`b.registrydns.co`
	NS	`c.registrydns.co`
	NS	`d.registrydns.co`
	SOA	`ns0.centralnic.net`hostmaster@centralnic.net serial=1759619894

Same first word

voidworks.co

voidworks.de

DNS History

15 records (8 active, 7 former)

○NSdns1.registrar-servers.com2015-07-25 → 2017-03-26 · 4 obs

● 2015-07-25 05:14:52
● 2017-03-26 01:33:44
○ 2026-03-20 20:45:58
○ 2026-03-28 00:01:10

○NSdns2.registrar-servers.com2015-07-25 → 2017-03-26 · 4 obs

● 2015-07-25 05:14:52
● 2017-03-26 01:33:44
○ 2026-03-20 20:45:58
○ 2026-03-28 00:01:10

○NSdns3.registrar-servers.com2015-07-25 → 2016-02-23 · 4 obs

● 2015-07-25 05:14:52
● 2016-02-23 10:49:46
○ 2016-07-09 16:20:06
○ 2026-03-28 00:01:10

○NSdns4.registrar-servers.com2015-07-25 → 2016-02-23 · 4 obs

● 2015-07-25 05:14:52
● 2016-02-23 10:49:46
○ 2016-07-09 16:20:06
○ 2026-03-28 00:01:10

○NSdns5.registrar-servers.com2015-07-25 → 2016-02-23 · 4 obs

● 2015-07-25 05:14:52
● 2016-02-23 10:49:46
○ 2016-07-09 16:20:06
○ 2026-03-28 00:01:10

●NSpdns1.registrar-servers.com2026-03-20 → 2026-03-28 · 3 obs

○ 2017-03-26 01:33:44
● 2026-03-20 20:45:58
● 2026-03-28 00:01:10

●NSpdns2.registrar-servers.com2026-03-20 → 2026-03-28 · 3 obs

○ 2017-03-26 01:33:44
● 2026-03-20 20:45:58
● 2026-03-28 00:01:10

●MXalt1.aspmx.l.google.com2015-07-25 → 2026-03-28 · 2 obs

● 2015-07-25 05:14:52
● 2026-03-28 00:01:10

●MXalt2.aspmx.l.google.com2015-07-25 → 2026-03-28 · 2 obs

● 2015-07-25 05:14:52
● 2026-03-28 00:01:10

●MXaspmx.l.google.com2015-07-25 → 2026-03-28 · 2 obs

● 2015-07-25 05:14:52
● 2026-03-28 00:01:10

●MXaspmx2.googlemail.com2015-07-25 → 2026-03-28 · 2 obs

● 2015-07-25 05:14:52
● 2026-03-28 00:01:10

●MXaspmx3.googlemail.com2015-07-25 → 2026-03-28 · 2 obs

● 2015-07-25 05:14:52
● 2026-03-28 00:01:10

○A173.203.204.1232015-07-25 → 2016-07-09 · 4 obs

● 2015-07-25 05:14:52
● 2016-07-09 16:20:06
○ 2017-03-26 01:33:44
○ 2026-03-28 00:01:10

○A192.64.119.272017-03-26 → 2017-03-26 · 4 obs

○ 2016-07-09 16:20:06
● 2017-03-26 01:33:44
○ 2026-03-20 20:45:58
○ 2026-03-28 00:01:10

●A198.202.211.12026-03-20 → 2026-03-28 · 3 obs

○ 2017-03-26 01:33:44
● 2026-03-20 20:45:58
● 2026-03-28 00:01:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
co	a.registrydns.co, b.registrydns.co, c.registrydns.co, d.registrydns.co	-
voidworks.co	pdns1.registrar-servers.com, pdns2.registrar-servers.com	-

✅ Authoritative Response

Server:156.154.133.100

NS records: pdns1.registrar-servers.com, pdns2.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for voidworks.co (unsigned zone)

⏱️ Timing

Total: 391ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`198.202.211.1`
NS	2	`pdns1.registrar-servers.com, pdns2.registrar-servers.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
TXT	5	`v=spf1 include:servers.mcsv.net ?all, MS=7F3B3B426D77AF5919E924173D9FC61DD9777...`
SOA	1	`pdns1.registrar-servers.com hostmaster.r`

Analysis

IP Addresses

voidworks.co resolves to one IP number: 198.202.211.1.

Other host names, for instance leadengine.ai, simplon.co, hotelcariongo.com, chmemorycare.com and mgmt.com.au share IP numbers with voidworks.co.

Name Servers

voidworks.co's delegation uses two name servers: pdns1.registrar-servers.com and pdns2.registrar-servers.com.

voidworks.co uses the same name server setup as other domains, such as tikcolor.com, trac.network, bigelow.org, kuhl.tv and daytime.com.au.

voidworks.co at least partially shares name servers with other domains, for example setse.org.mx.

Host names with two IPs:

pdns1.registrar-servers.com points to 2610:a1:1024::100 and 156.154.132.100

pdns2.registrar-servers.com points to 2610:a1:1025::100 and 156.154.133.100

Mail Servers

voidworks.co is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.

voidworks.co shares at least some mail servers with other domains, for example ccdeh.com, kresa.com.pe, gestionc.es, huimin.com.tw and traveltino.com.