`check-updates.net`

DNSSEC	⚠️ Not signed
A	2a01:4f8:172:35ec::2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
A	188.40.59.208^{🇩🇪 Hetzner188.40.0.0/16 HETZNER-RZ-FKS-BLK1}
NS	`ns.check-updates.net` ⭐
		A	2a01:4f8:172:35ec::2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
		A	138.201.138.240^{🇩🇪 Hetzner138.201.0.0/16 HETZNER-RZ-BLK-ERX4}
			PTR	`pfsense.kirub2.de`
NS	`b.ns14.net`
		A	2001:8d8:fe:53:217:160:81:160^{🇩🇪 IONOS-AS2001:8d8:fe::/47 IONOS AS8560 anycast more specific}
			PTR	`ns-ix1.ui-dns.biz`
		A	217.160.81.160^{🇩🇪 IONOS-AS217.160.80.0/22 AS8560 anycast more specific}
			PTR	`ns-ix1.ui-dns.biz`
NS	`c.ns14.net`
		A	2607:f1c0:fe:53:185:132:35:160^{🇺🇸 IONOS-ANYCAST2607:f1c0:fe::/47 AS8560 global anycast services (more specific) 1&1 IONOS Inc. 701 Lee Rd, Suite 300 Chesterbrook, PA 19087 US}
			PTR	`ns-ix1.ui-dns.org`
		A	185.132.35.160^{🇩🇪 IONOS-ANYCAST185.132.32.0/22 IONOS DNSAS (eBGP DNS)}
			PTR	`ns-ix1.ui-dns.org`
NS	`d.ns14.net`
		A	2607:f1c0:fe:53:185:132:34:160^{🇺🇸 IONOS-ANYCAST2607:f1c0:fe::/47 AS8560 global anycast services (more specific) 1&1 IONOS Inc. 701 Lee Rd, Suite 300 Chesterbrook, PA 19087 US}
			PTR	`ns-ix1.ui-dns.com`
		A	185.132.34.160^{🇩🇪 IONOS-ANYCAST185.132.32.0/22 IONOS DNSAS (eBGP DNS)}
			PTR	`ns-ix1.ui-dns.com`
MX	`mail.check-updates.net` ⭐
		A	2a01:4f8:140:82a6::2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
		A	2a01:4f8:150:1103::2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
		A	2a01:4f8:151:73a5::2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
		A	2a01:4f8:221:4202::2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
		A	2a01:4f8:222:27c1::2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
		A	46.4.96.137^{🇩🇪 Hetzner46.4.0.0/16 HETZNER-RZ-FKS-BLK3}
			PTR	`static.137.96.4.46.clients.your-server.de`
		A	88.198.24.108^{🇩🇪 Hetzner88.198.0.0/16 HETZNER-RZ-NBG-BLK4}
			PTR	`static.88-198-24-108.clients.your-server.de`
		A	88.198.50.103^{🇩🇪 Hetzner88.198.0.0/16 HETZNER-RZ-NBG-BLK4}
			PTR	`static.88-198-50-103.clients.your-server.de`
		A	176.9.75.42^{🇩🇪 Hetzner176.9.0.0/16 HETZNER-RZ-FKS-BLK4}
			PTR	`static.42.75.9.176.clients.your-server.de`
		A	176.9.119.170^{🇩🇪 Hetzner176.9.0.0/16 HETZNER-RZ-FKS-BLK4}
			PTR	`static.170.119.9.176.clients.your-server.de`
TXT	`type=2`
TXT	`v=spf1 exists:%{h}.h.%{ir}._spf.check-updates.net ?all`
SOA	`ns.check-updates.net`hostmaster@check-updates.net 2026-02-23 #0

`net`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1780530174

⚠️ On DNS blocklist: tif
WOT: SUSPICIOUS (11/100)

Subdomains

mail.check-updates.net

ns.check-updates.net

Same first word

check-updates.net

DNS History

15 records (7 active, 8 former)

●NSb.ns14.net2017-02-07 → 2026-06-04 · 2 obs

● 2017-02-07 19:13:14
● 2026-06-04 00:09:48

●NSc.ns14.net2017-02-07 → 2026-06-04 · 2 obs

● 2017-02-07 19:13:14
● 2026-06-04 00:09:48

●NSd.ns14.net2017-02-07 → 2026-06-04 · 2 obs

● 2017-02-07 19:13:14
● 2026-06-04 00:09:48

●NSns.check-updates.net2017-02-07 → 2026-06-04 · 2 obs

● 2017-02-07 19:13:14
● 2026-06-04 00:09:48

●MXmail.check-updates.net2019-12-26 → 2026-06-04 · 3 obs

○ 2017-02-07 19:13:14
● 2019-12-26 17:38:10
● 2026-06-04 00:09:48

○MXsmtp-in.eu.cloudmxguard.com2017-02-07 → 2017-02-07 · 3 obs

● 2017-02-07 19:13:14
○ 2019-12-26 17:38:10
○ 2026-06-04 00:09:48

○MXsmtp-in.us.cloudmxguard.com2017-02-07 → 2017-02-07 · 3 obs

● 2017-02-07 19:13:14
○ 2019-12-26 17:38:10
○ 2026-06-04 00:09:48

○A159.65.245.162019-12-26 → 2019-12-26 · 3 obs

● 2019-12-26 17:38:10
○ 2026-02-24 19:12:14
○ 2026-06-04 00:09:48

○A178.128.243.1712019-12-26 → 2019-12-26 · 3 obs

● 2019-12-26 17:38:10
○ 2026-02-24 19:12:14
○ 2026-06-04 00:09:48

●A188.40.59.2082026-02-24 → 2026-06-04 · 3 obs

○ 2019-12-26 17:38:10
● 2026-02-24 19:12:14
● 2026-06-04 00:09:48

○A206.189.153.1352019-12-26 → 2019-12-26 · 3 obs

● 2019-12-26 17:38:10
○ 2026-02-24 19:12:14
○ 2026-06-04 00:09:48

○A2400:6180:0:d1::374:90012019-12-26 → 2019-12-26 · 3 obs

● 2019-12-26 17:38:10
○ 2026-02-24 19:12:14
○ 2026-06-04 00:09:48

○A2604:a880:800:a1::821:d0012019-12-26 → 2019-12-26 · 3 obs

● 2019-12-26 17:38:10
○ 2026-02-24 19:12:14
○ 2026-06-04 00:09:48

●A2a01:4f8:172:35ec::22026-02-24 → 2026-06-04 · 3 obs

○ 2019-12-26 17:38:10
● 2026-02-24 19:12:14
● 2026-06-04 00:09:48

○A2a03:b0c0:2:f0::2f:60012019-12-26 → 2019-12-26 · 3 obs

● 2019-12-26 17:38:10
○ 2026-02-24 19:12:14
○ 2026-06-04 00:09:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net...	-
check-updates.net	b.ns14.net, c.ns14.net, d.ns14.net	6 records

✅ Authoritative Response

Server:185.132.35.160

NS records: b.ns14.net, c.ns14.net, d.ns14.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for check-updates.net (unsigned zone)

⏱️ Timing

Total: 372ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`188.40.59.208`
AAAA	1	`2a01:4f8:172:35ec::2`
NS	3	`d.ns14.net, b.ns14.net...`
MX	1	`mail.check-updates.net (pri: 100)`
TXT	2	`type=2, v=spf1 exists:%{h}.h.%{ir}._spf.check-up`
SOA	1	`ns.check-updates.net hostmaster.check-up`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (b.ns14.net, b.ns14.net, c.ns14.net...)

Analysis

Hierarchy

The parent domain of mail.check-updates.net and ns.check-updates.net is check-updates.net.

IP Addresses

check-updates.net points to two IP numbers: 188.40.59.208 and 2a01:4f8:172:35ec::2.

Among the host names that share IP numbers with check-updates.net are 66-111-53-75.static.sagonet.net, 66-118-156-59.static.sagonet.net, 66-118-190-8.static.sagonet.net and two others.

Name Servers

check-updates.net carries NS records pointing to 4 name servers: ns.check-updates.net, b.ns14.net, c.ns14.net and d.ns14.net.

check-updates.net has at least partial name server overlap with other domains, such as antes.be, der-sueden.net, vitaball.sc and two others.

It is common to see these name servers used together with name servers a.ns14.net and hidden-dns2.waz-mediengruppe.de.

ns.check-updates.net, b.ns14.net, c.ns14.net and d.ns14.net all point to exactly two IP numbers each: ns.check-updates.net → 138.201.138.240 and 2a01:4f8:172:35ec::2; b.ns14.net → 217.160.81.160 and 2001:8d8:fe:53:217:160:81:160; c.ns14.net → 185.132.35.160 and 2607:f1c0:fe:53:185:132:35:160; d.ns14.net → 185.132.34.160 and 2607:f1c0:fe:53:185:132:34:160.

Mail Servers

check-updates.net routes its mail through a single mail server, mail.check-updates.net.

check-updates.net uses the same mail servers as ns.check-updates.net and mail.check-updates.net, among others.

mail.check-updates.net directs to 10 IP numbers, specifically 46.4.96.137, 88.198.24.108, 88.198.50.103 and seven others.

check-updates.net - robtex.com