SurfaceMap › r › rammstein.de

rammstein.de

Checked 2026-10-21 23:52 UTC · first added 2026-10-21
✗Problems found Score 60 of 100

Domain & DNS

fail

22 passed 2 warn 1 failed

Areas

iRegistration iDelegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.virtualhosts.de (2a02:e00:fff0:ba::1): dial tcp [2a02:e00:fff0:ba::1]:53: connect: connection refused; ns2.virtualhosts.de (2a02:e00:ffed:90::1): dial tcp [2a02:e00:ffed:90::1]:53: connect: connection refused; ns3.virtualhosts.eu (80.83.124.49): dial tcp 80.83.124.49:53: connect: connection refused; ns3.virtualhosts.eu (2a02:e00:ffec:d8::1): dial tcp [2a02:e00:ffec:d8::1]:53: connect: connection refused.
    #19
  • !
    No EDNS
    Nameservers · These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns1.virtualhosts.de (195.128.160.129), ns1.virtualhosts.de (2a02:e00:fff0:ba::1), ns2.virtualhosts.de (195.68.246.129), ns2.virtualhosts.de (2a02:e00:ffed:90::1), ns3.virtualhosts.eu (80.83.124.49), ns3.virtualhosts.eu (2a02:e00:ffec:d8::1).
    #20
  • !
    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 rammstein.de ›

Mail

warn

20 passed 8 warn 0 failed

Areas

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

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: mail.rammstein.de
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Key in test mode
    DKIM · These keys have t=y, so receivers treat DKIM failures as a test: default. Remove t=y once DKIM works.
    #24
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 80.83.113.38 (mail.rammstein.de). Ask your hosting provider to set one.
    #30
  • !
    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 rammstein.de ›