`maintask.pro`

DNSSEC	⚠️ Not signed
A	2001:1528:240::15^{🇨🇿 CASABLANCA-AS2001:1528::/32 Casablanca INT v6 network}
		PTR	`krios.blueboard.cz`
A	217.11.249.139^{🇨🇿 CASABLANCA-AS217.11.248.0/23 Casablanca INT}
NS	`shinzon.blueboard.cz` ⭐
		A	2a00:1ed0:45::b^{🇨🇿 VSHOSTING2a00:1ed0::/32}
			PTR	`shinzon.blueboard.cz`
		A	178.251.187.7^{🇨🇿 VSHOSTING178.251.184.0/21}
			PTR	`shinzon.blueboard.cz`
NS	`ns2.blueboard.cz`
		A	2a01:4f8:13b:8d4::2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
		A	195.201.57.122^{🇩🇪 Hetzner195.201.0.0/16 HETZNER-DC}
			PTR	`ns2.blueboard.cz`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`v=spf1 a mx include:_spf.google.com ~all`
SOA	`shinzon.blueboard.cz`hostmaster@blueboard.cz 2017-02-24 #1

`pro`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.pro.afilias-nst.info` ⭐
	NS	`a2.pro.afilias-nst.info`
	NS	`b0.pro.afilias-nst.org`
	NS	`b2.pro.afilias-nst.org`
	NS	`c0.pro.afilias-nst.info`
	NS	`d0.pro.afilias-nst.org`
	SOA	`a0.pro.afilias-nst.info`hostmaster@donuts.email serial=1783840294

Same first word

maintask.pro

maintask.com

maintask.dk

maintask.net

Similar names

DNS History

9 records (9 active, 0 former)

●NSns2.blueboard.cz2020-01-04 → 2026-07-12 · 2 obs

● 2020-01-04 16:45:40
● 2026-07-12 07:37:58

●NSshinzon.blueboard.cz2020-01-04 → 2026-07-12 · 2 obs

● 2020-01-04 16:45:40
● 2026-07-12 07:37:58

●MXalt1.aspmx.l.google.com2020-01-04 → 2026-07-12 · 2 obs

● 2020-01-04 16:45:40
● 2026-07-12 07:37:58

●MXalt2.aspmx.l.google.com2020-01-04 → 2026-07-12 · 2 obs

● 2020-01-04 16:45:40
● 2026-07-12 07:37:58

●MXalt3.aspmx.l.google.com2020-01-04 → 2026-07-12 · 2 obs

● 2020-01-04 16:45:40
● 2026-07-12 07:37:58

●MXalt4.aspmx.l.google.com2020-01-04 → 2026-07-12 · 2 obs

● 2020-01-04 16:45:40
● 2026-07-12 07:37:58

●MXaspmx.l.google.com2020-01-04 → 2026-07-12 · 2 obs

● 2020-01-04 16:45:40
● 2026-07-12 07:37:58

●A2001:1528:240::152020-01-04 → 2026-07-12 · 2 obs

● 2020-01-04 16:45:40
● 2026-07-12 07:37:58

●A217.11.249.1392020-01-04 → 2026-07-12 · 2 obs

● 2020-01-04 16:45:40
● 2026-07-12 07:37:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
pro	a0.pro.afilias-nst.info, d0.pro.afilias-nst.org, b2.pro.afilias-nst.org, b0.pro.afilias-nst.org...	12 records
maintask.pro	ns2.blueboard.cz, shinzon.blueboard.cz	-

✅ Authoritative Response

Server:195.201.57.122

NS records: ns2.blueboard.cz, shinzon.blueboard.cz

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for maintask.pro (unsigned zone)

⏱️ Timing

Total: 4042ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`217.11.249.139`
AAAA	1	`2001:1528:240::15`
NS	2	`ns2.blueboard.cz, shinzon.blueboard.cz`
MX	5	`alt3.aspmx.l.google.com (pri: 10), alt2.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 a mx include:_spf.google.com ~all`
SOA	1	`shinzon.blueboard.cz hostmaster.blueboar`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (a0.pro.afilias-nst.info, a0.pro.afilias-nst.info, d0.pro.afilias-nst.org...)

Analysis

IP Addresses

maintask.pro points to the IP addresses 217.11.249.139 and 2001:1528:240::15

iab.cz, jdemefandit.cz, s04.a013.ap.epiderma.pl and two other host names share IP numbers with maintask.pro.

Name Servers

maintask.pro has two authoritative name servers — ns2.blueboard.cz and shinzon.blueboard.cz.

maintask.pro uses the same name servers as several other domains — among them dinage.eu, gamoschem.com, lesba.sk and two more.

The name servers of maintask.pro overlap at least partially with those of other domains — among them tonireal.cz, divinorum.cz, saey.cz and two more.

The name servers jaguar.blueboard.cz, ns2.miniserver.cz and server.jerewan.cz are commonly seen alongside these name servers.

Both ns2.blueboard.cz and shinzon.blueboard.cz have two IP addresses each. ns2.blueboard.cz resolves to 195.201.57.122 and 2a01:4f8:13b:8d4::2; shinzon.blueboard.cz resolves to 178.251.187.7 and 2a00:1ed0:45::b.