lavera.de

Checked 21 October 2026, 23:11 UTC · via 8.8.8.8
!Passed with warnings
25 passed 4 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx ip4:151.189.187.13 ip4:151.189.187.14 ip4:188.114.96.7 ip4:188.114.97.7 ip4:151.189.187.8 ip4:20.50.178.65 include:spf.protection.outlook.com -all
DNS lookups
3 of 10
Void lookups
0 of 2

Checks

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

pass

p=reject (_dmarc.lavera.de)

Found

Record
v=DMARC1; p=reject; rua=mailto:097026a5daa5417ab7bab82437d15b8f@dmarc-reports.cloudflare.net; ruf=mailto:dmarc-reports@lavera.de; pct=100
Found at
_dmarc.lavera.de
External report address
mailto:097026a5daa5417ab7bab82437d15b8f@dmarc-reports.cloudflare.net (authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
pct100Percentage of mail the policy applies to
ruamailto:097026a5daa5417ab7bab82437d15b8f@dmarc-reports.cloudflare.netAggregate report addresses
rufmailto:dmarc-reports@lavera.deFailure report addresses

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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:097026a5daa5417ab7bab82437d15b8f@dmarc-reports.cloudflare.net
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: dkim, selector1, s1, s2

Found

Selectors
dkim, selector1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
dkimRSA 2048 bits
selector1RSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: dkim, selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: dkim, selector1, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: s2 (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
0lavera-de.mail.protection.outlook.comA 52.101.68.15 A 52.101.73.153 A 52.101.181.153 A 52.101.185.114 AAAA 2a01:111:f403:ca04::10 AAAA 2a01:111:f403:ca04::e AAAA 2a01:111:f403:ca04::4 AAAA 2a01:111:f403:ca3c::8mail-db6pr03cu00107.inbound.protection.outlook.com ✓ mail-as8pr05cu00401.inbound.protection.outlook.com ✓ mail-wa4pr04cu00101.inbound.protection.outlook.com ✓ mail-zrxpr04cu00102.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.inbound.protection.outlook.com ✓ mail-db8pr02cu00106.inbound.protection.outlook.com ✓ mail-db4pr02cu00204.inbound.protection.outlook.com ✓ mail-zrxpr05cu00100.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 · no TLS-RPT · DANE on 0 of 1 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
lavera-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
  • 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