SurfaceMap › r › rtl2.de

rtl2.de

Checked 2026-10-22 00:01 UTC · first added 2026-10-21

✗Problems found Score 57 of 100

Domain & DNS

fail

17 passed 5 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

✗

Nameservers not responding

Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns1.rtl2.de (2a0a:d480:1:1::100): read udp [2a01:4f8:1c1c:eebf::1]:36634->[2a0a:d480:1:1::100]:53: i/o timeout; pfire-1.rtl2.de (2a0a:d480:1:1::100): read udp [2a01:4f8:1c1c:eebf::1]:46420->[2a0a:d480:1:1::100]:53: i/o timeout; pfire-2.rtl2.de (2a0a:d480:1:1::102): read udp [2a01:4f8:1c1c:eebf::1]:55299->[2a0a:d480:1:1::102]:53: i/o timeout.

#14
!

NS sets differ

Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: pfire-1.rtl2.de, pfire-2.rtl2.de. ns1.cc-net.de, ns1.rtl2.de, ns2.cc-net.de, pfire-1.rtl2.de, pfire-2.rtl2.de report NS ns1.cc-net.de ns1.rtl2.de ns2.cc-net.de pfire-1.rtl2.de pfire-2.rtl2.de.

#7
!

Software version disclosed

Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.cc-net.de: "9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6_10.3"; ns1.rtl2.de: "NSD 4.15.0"; ns2.cc-net.de: "9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6_10.3"; pfire-1.rtl2.de: "NSD 4.15.0"; pfire-2.rtl2.de: "NSD 4.15.0". Hide or replace the version string.

#17
!

Serials differ

SOA · The nameservers serve different versions of the zone: 1791966973 on ns1.cc-net.de (213.183.80.5), ns1.rtl2.de (185.181.224.4), ns2.cc-net.de (213.183.81.5), pfire-1.rtl2.de (185.181.224.4); 1791966983 on pfire-2.rtl2.de (185.181.224.6). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

#22
!

Unusual SOA timers

SOA · refresh 10m is outside 20m–1d; retry 10m should be shorter than refresh 10m; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 10m, retry 10m, expire 1d, negative TTL 10m.

#23
!

Not signed

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

#27

Recent checks

✗

Full report

Domain & DNS report for rtl2.de ›

Mail

warn

23 passed 6 warn 0 failed

Areas

✓SPF !DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

!

Policy: quarantine

DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.

#4
!

Not enabled

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8
!

Single MX host, no backup

MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.

#12
!

Subdomains unprotected (sp=none)

DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.

#20
!

1024-bit DKIM key

DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits). Rotate to a 2048-bit key.

#23
!

Not configured

TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.

#32

Recent checks

Full report

Mail report for rtl2.de ›