`ewerk-server01.de`

DNSSEC	⚠️ Not signed
A	178.63.102.2^{🇩🇪 Hetzner178.63.0.0/16 HETZNER-RZ-FKS-BLK2}
		PTR	`trier.ewerk-server01.de`
NS	`ns1.first-ns.de` ⭐
		A	2a01:4f8:0:a101::a:1^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
			PTR	`ns1.first-ns.de`
		A	213.239.242.238^{🇩🇪 Hetzner213.239.192.0/18 HETZNER-RZ-NBG-BLK2}
			PTR	`ns1.first-ns.de`
NS	`robotns2.second-ns.de`
		A	2a01:4f8:0:1::5ddc:2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
			PTR	`robotns2.second-ns.de`
		A	213.133.100.103^{🇩🇪 Hetzner213.133.96.0/19 HETZNER-RZ-NBG-BLK1}
			PTR	`robotns2.second-ns.de`
NS	`robotns3.second-ns.com`
		A	2001:67c:192c::add:a3^{🇩🇪 NORIS-NETWORK2001:67c:192c::/48}
			PTR	`robotns3.second-ns.com`
		A	193.47.99.3^{🇩🇪 NORIS-NETWORK193.47.99.0/24}
			PTR	`robotns3.second-ns.com`
MX	`trier.ewerk-server01.de` ⭐
		A	2a01:4f8:121:5128::2^{🇩🇪 Hetzner2a01:4f8::/32 HETZNER-IPv6-BLK}
			PTR	`trier.ewerk-server01.de`
		A	178.63.102.2^{🇩🇪 Hetzner178.63.0.0/16 HETZNER-RZ-FKS-BLK2}
			PTR	`trier.ewerk-server01.de`
TXT	`v=spf1 mx a:trier.ewerk-server01.de -all`
SOA	`ns1.first-ns.de`dns@hetzner.com 2026-04-14 #0

`de`

	DNSSEC	🔒 Signed (DS record present)
	NS	`f.nic.de` ⭐
	NS	`a.nic.de`
	NS	`l.de.net` ⚠️ Not in parent delegation
	NS	`n.de.net` ⚠️ Not in parent delegation
	NS	`s.de.net` ⚠️ Not in parent delegation
	NS	`z.nic.de`
	SOA	`f.nic.de`dns-operations@denic.de serial=1776681924

Subdomains

trier.ewerk-server01.de

Same first word

ewerk-server01.de

DNS History

5 records (5 active, 0 former)

●NSns1.first-ns.de2018-10-03 → 2026-04-20 · 2 obs

● 2018-10-03 04:12:38
● 2026-04-20 11:09:46

●NSrobotns2.second-ns.de2018-10-03 → 2026-04-20 · 2 obs

● 2018-10-03 04:12:38
● 2026-04-20 11:09:46

●NSrobotns3.second-ns.com2018-10-03 → 2026-04-20 · 2 obs

● 2018-10-03 04:12:38
● 2026-04-20 11:09:46

●MXtrier.ewerk-server01.de2018-10-03 → 2026-04-20 · 2 obs

● 2018-10-03 04:12:38
● 2026-04-20 11:09:46

●A178.63.102.22018-10-03 → 2026-04-20 · 2 obs

● 2018-10-03 04:12:38
● 2026-04-20 11:09:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
de	a.nic.de, f.nic.de, z.nic.de	-
ewerk-server01.de	ns1.first-ns.de, robotns2.second-ns.de, robotns3.second-ns.com	-

✅ Authoritative Response

Server:193.47.99.3

NS records: ns1.first-ns.de, robotns2.second-ns.de, robotns3.second-ns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ewerk-server01.de (unsigned zone)

⏱️ Timing

Total: 1586ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`178.63.102.2`
NS	3	`ns1.first-ns.de, robotns2.second-ns.de...`
MX	1	`trier.ewerk-server01.de (pri: 10)`
TXT	1	`v=spf1 mx a:trier.ewerk-server01.de -all`
SOA	1	`ns1.first-ns.de dns.hetzner.com`

Analysis

Hierarchy

The parent of trier.ewerk-server01.de is ewerk-server01.de.

IP Addresses

ewerk-server01.de points to an IP address: 178.63.102.2.

other host names include trier.ewerk-server01.de, igoras.de, mail.webment.de, ns1.igoras.com and ns.igoras.com; they share IP numbers with ewerk-server01.de.

Name Servers

ewerk-server01.de is delegated to three name servers robotns3.second-ns.com, ns1.first-ns.de and robotns2.second-ns.de.

ewerk-server01.de at least partially shares name servers with other domains, for instance savvysolutions.de, bitquadrat.de, car2fly.de, fortis-it.net and crembo.de.

These name servers are commonly used alongside ns1.your-server.de.

Host names with two IP numbers:

robotns3.second-ns.com points to 2001:67c:192c::add:a3 and 193.47.99.3; ns1.first-ns.de points to 2a01:4f8:0:a101::a:1 and 213.239.242.238; robotns2.second-ns.de points to 2a01:4f8:0:1::5ddc:2 and 213.133.100.103.

Mail Servers

ewerk-server01.de is handled by a single mail server, trier.ewerk-server01.de.

trier.ewerk-server01.de resolves to two IPs: 2a01:4f8:121:5128::2 and 178.63.102.2.

ewerk-server01.de - robtex.com