SurfaceMap › c › crif.de

crif.de

Checked 2026-10-21 22:11 UTC · first added 2026-10-21
✗Problems found Score 75 of 100

Domain & DNS

warn

22 passed 3 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-161.akam.net: "41824.5"; a1-161.akam.net: "41824.7"; a13-66.akam.net: "41824.5"; a13-66.akam.net: "41824.4"; a14-67.akam.net: "48878.33"; a14-67.akam.net: "48878.30"; a20-64.akam.net: "48878.33"; a20-64.akam.net: "48878.26"; a3-65.akam.net: "41824.7"; a3-65.akam.net: "41824.11"; a4-66.akam.net: "48878.33". 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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 5m; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for crif.de ›

Mail

fail

15 passed 2 warn 1 failed

Areas

✓SPF ✗DMARC ✓DKIM !DNSSEC !MX iBIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    No MX records
    MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").
    #9

Recent checks

✗

Full report

Mail report for crif.de ›