berlin1.de

Checked 21 October 2026, 21:37 UTC · via 8.8.8.8
✗Problems found
12 passed 5 warnings 2 failed 3 info

SPF

fail

No SPF record found

Checks

  • ✗
    No SPF record
    No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6

DMARC

warn

p=quarantine (_dmarc.berlin1.de)

Found

Record
v=DMARC1; p=quarantine; sp=quarantine; pct=100; rua=mailto:dmarc_report@funkemedien.de
Found at
_dmarc.berlin1.de
External report address
mailto:dmarc_report@funkemedien.de (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spquarantineSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc_report@funkemedien.deAggregate report addresses

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc_report@funkemedien.de
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.berlin1.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
10mx0.asv.de(does not resolve)
20mx1.asv.de(does not resolve)
30mx2.asv.de(does not resolve)
40mx3.asv.de(does not resolve)

Checks

  • ✓ 4 MX records #9
    Found 4 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: mx0.asv.de, mx1.asv.de, mx2.asv.de, mx3.asv.de
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mx0.asv.de, mx1.asv.de, mx2.asv.de, mx3.asv.de
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.

TLS

warn

no MTA-STS · no TLS-RPT · DANE on 0 of 4 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx0.asv.denone-
mx1.asv.denone-
mx2.asv.denone-
mx3.asv.denone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38