ifa-berlin.de

Checked 21 October 2026, 22:51 UTC · via 8.8.8.8
✗Problems found
9 passed 3 warnings 4 failed 2 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

fail

No DMARC record found

Checks

  • ✗
    No DMARC record
    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

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.ifa-berlin.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

1 mail server

Found

PriorityHostRecordsReverse DNS
50mail.ifa-berlin.deA 92.204.219.1919.219.204.92.host.secureserver.net ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mail.ifa-berlin.de
    #11
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 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.
  • ✓ Reverse DNS confirmed #30
    All 1 MX address have a PTR record that resolves back to them.

TLS

fail

MTA-STS record without policy · TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record
v=STSv1; id=202605191000;
Policy URL
https://mta-sts.ifa-berlin.de/.well-known/mta-sts.txt
Policy error
Get "https://mta-sts.ifa-berlin.de/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.ifa-berlin.de on 127.0.0.53:53: no such host
TLS-RPT record
v=TLSRPTv1; rua=mailto:webmaster@pitservices.de

DANE (TLSA records)

MX hostTLSADNSSEC
mail.ifa-berlin.denone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 202605191000.
  • ✗
    Policy not reachable
    The MTA-STS record exists but the policy could not be fetched, so senders ignore MTA-STS: Get "https://mta-sts.ifa-berlin.de/.well-known/mta-sts.txt": dial tcp: lookup mta-sts.ifa-berlin.de on 127.0.0.53:53: no such host.
    #33
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:webmaster@pitservices.de
  • 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