SurfaceMap › u › uniklinikum-saarland.de

uniklinikum-saarland.de

Checked 2026-10-22 00:50 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

fail

19 passed 3 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: forest.uniklinikum-saarland.de (134.96.149.1): read udp 46.225.38.91:54616->134.96.149.1:53: i/o timeout; gump.uniklinikum-saarland.de (134.96.149.2): read udp 46.225.38.91:41700->134.96.149.2: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: forest.uniklinikum-saarland.de, gump.uniklinikum-saarland.de. deneb.dfn.de, dns-1.dfn.de, dns-2.dfn.de, nse1.med-rz.uniklinik-saarland.de, nse1.uks.eu report NS deneb.dfn.de dns-1.dfn.de dns-2.dfn.de forest.uniklinikum-saarland.de gump.uniklinikum-saarland.de nse1.med-rz.uniklinik-saarland.de nse1.uks.eu.
    #7
  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d. Current values: refresh 15m, retry 10m, expire 40d, negative TTL 1h.
    #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 uniklinikum-saarland.de ›

Mail

warn

26 passed 5 warn 0 failed

Areas

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

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mgate1.uks.eu, mgate2.uks.eu
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: default (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
  • !
    No certificate (a=)
    BIMI · The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.
    #38

Recent checks

!

Full report

Mail report for uniklinikum-saarland.de ›