dial.de

Checked 21 October 2026, 22:14 UTC · via 8.8.8.8
!Passed with warnings
26 passed 6 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 a:mout.kundenserver.de include:eu-central-1.amazonses.com ip4:86.39.202.107 ip4:178.63.148.167 ip4:212.29.33.164 include:idw.emailr.com include:spf.protection.outlook.com include:spf-de.emailsignatures365.com include:spf.mandrillapp.com include:spf.mailjet.com -all
DNS lookups
8 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 8 of 10 DNS lookups #2
    SPF record needs 8 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

warn

p=quarantine (_dmarc.dial.de)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc_reports@dial.de;
Found at
_dmarc.dial.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc_reports@dial.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_reports@dial.de
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector1, key, s1, s2

Found

Selectors
selector1, key, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
keyRSA 1024 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, key, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, key, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: key (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

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
0dial-de.mail.protection.outlook.comA 52.101.168.0 A 52.101.170.1 A 52.101.170.2 A 52.101.170.0 AAAA 2a01:111:f403:ca2d::2 AAAA 2a01:111:f403:ca2d::1 AAAA 2a01:111:f403:ca27:: AAAA 2a01:111:f403:ca2d::mail-beup281cu00100.inbound.protection.outlook.com ✓ mail-fr4p281cu03101.inbound.protection.outlook.com ✓ mail-fr6p281cu00202.inbound.protection.outlook.com ✓ mail-fr5p281cu00500.inbound.protection.outlook.com ✓ mail-fr6p281cu00202.inbound.protection.outlook.com ✓ mail-fr4p281cu03101.inbound.protection.outlook.com ✓ mail-beup281cu00100.inbound.protection.outlook.com ✓ mail-fr5p281cu00500.inbound.protection.outlook.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

TLS-RPT record
v=TLSRPTv1; rua=mailto:tlsrpt@dial.de;

DANE (TLSA records)

MX hostTLSADNSSEC
dial-de.mail.protection.outlook.comnone-

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
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:tlsrpt@dial.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

warn

https://www.dial.de/fileadmin/images/bimi-dial.svg

Found

Record
v=BIMI1; l=https://www.dial.de/fileadmin/images/bimi-dial.svg; avp=brand;
Found at
default._bimi.dial.de
Logo
https://www.dial.de/fileadmin/images/bimi-dial.svg

Checks

  • !
    No certificate (a=)
    The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.
    #38
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.