SurfaceMap › l › livingathome.de

livingathome.de

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

Domain & DNS

warn

24 passed 2 warn 0 failed

Areas

iRegistration ✓Delegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.dts-online.net: "Felix' DNS Server V0.1 <script>alert('hello, world');</script>"; ns3.icsmedia.de: "DNS Server V0.1' OR 1=1; DROP TABLE accounts; '"; ns4.icsmedia.de: "DNS Server V0.1' OR 1=1; DROP TABLE accounts; '". Hide or replace the version string.
    #17
  • !
    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 livingathome.de ›

Mail

fail

14 passed 5 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    No DKIM keys published
    DKIM · _domainkey.livingathome.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    7 of 10 DNS lookups, with problems
    SPF · SPF record needs 7 DNS lookups (limit is 10). Problems found: include:salesforcespf.lv.deip4:212.101.207.0/24 does not exist or has no records.
    #2
  • !
    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
  • !
    1 void lookup
    SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    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 livingathome.de ›