lexware.de

Checked 21 October 2026, 23:12 UTC · via 8.8.8.8
!Passed with warnings
29 passed 3 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:haufe.de include:spf.protection.outlook.com include:_spf.google.com include:147556767.spf06.hubspotemail.net -all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 7 of 10 DNS lookups #2
    SPF record needs 7 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.lexware.de)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc+aggregated@reports.nicmanager.net;
Found at
_dmarc.lexware.de
External report address
mailto:dmarc+aggregated@reports.nicmanager.net (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc+aggregated@reports.nicmanager.netAggregate 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+aggregated@reports.nicmanager.net
  • ✓ 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

pass

Selectors: google

Found

Selectors
google
_domainkey
NOERROR
SelectorKeyFlags
googleRSA 2048 bits

Checks

  • ✓ Keys found: google #7
    DKIM keys found for this domain with selectors: google
  • ✓ Strong keys #23
    DKIM keys are strong enough: google: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
21203, 37658
Signatures valid until
29 October 2026, 00:00 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-10-29 #21
    DNSKEY signatures are valid until 2026-10-29T00:00:00Z.

MX

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
10mail.haufe.deA 185.150.247.40mail.haufe.de ✓
20mail2.haufe.deA 185.150.247.41mail2.haufe.de ✓
30mail3.haufe.deA 185.150.247.42mail3.haufe.de ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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.haufe.de, mail2.haufe.de, mail3.haufe.de
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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 3 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mail.haufe.denone-
mail2.haufe.denone-
mail3.haufe.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

pass

https://vmc.digicert.com/43f6d7ad-30ff-4195-92a7-fb83f7f85dfd.svg

Found

Record
v=BIMI1; l=https://vmc.digicert.com/43f6d7ad-30ff-4195-92a7-fb83f7f85dfd.svg; a=https://vmc.digicert.com/43f6d7ad-30ff-4195-92a7-fb83f7f85dfd.pem
Found at
default._bimi.lexware.de
Logo
https://vmc.digicert.com/43f6d7ad-30ff-4195-92a7-fb83f7f85dfd.svg
Certificate
https://vmc.digicert.com/43f6d7ad-30ff-4195-92a7-fb83f7f85dfd.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://vmc.digicert.com/43f6d7ad-30ff-4195-92a7-fb83f7f85dfd.svg; certificate: https://vmc.digicert.com/43f6d7ad-30ff-4195-92a7-fb83f7f85dfd.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.