deutsche-familienversicherung.de

Checked 21 October 2026, 22:13 UTC · via 8.8.8.8
✗Problems found
21 passed 5 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.protection.outlook.com include:145795722.spf07.hubspotemail.net include:amazonses.com include:_smtp.udag.de include:spf.dynect.net include:nl2go.deutsche-familienversicherung.de include:pso-vertrieb.deutsche-familienversicherung.de include:spf.mailjet.com ip6:2a02:2e0:40d:16:d::11 ip4:82.98.67.89 ip4:217.111.79.222 ip4:139.1.128.128/25 ip4:212.19.45.181 ip4:212.19.46.25 ip4:212.19.46.35 ip4:217.111.79.217 ip4:139.1.158.11 ~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

fail

p=none (_dmarc.deutsche-familienversicherung.de)

Found

Record
v=DMARC1; p=none; rua=mailto:rua-dfv@cyber-samurai.net; ruf=mailto:ruf-dfv@cyber-samurai.net; sp=none; aspf=r; adkim=r
Found at
_dmarc.deutsche-familienversicherung.de
External report address
mailto:rua-dfv@cyber-samurai.net (not authorized)
External report address
mailto:ruf-dfv@cyber-samurai.net (not authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
ruamailto:rua-dfv@cyber-samurai.netAggregate report addresses
rufmailto:ruf-dfv@cyber-samurai.netFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:rua-dfv@cyber-samurai.net
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:rua-dfv@cyber-samurai.net (needs deutsche-familienversicherung.de._report._dmarc.cyber-samurai.net); mailto:ruf-dfv@cyber-samurai.net (needs deutsche-familienversicherung.de._report._dmarc.cyber-samurai.net). Ask the report provider to publish the record, or check the address.
    #29

DKIM

warn

Selectors: default, dkim, selector1

Found

Selectors
default, dkim, selector1
_domainkey
NOERROR
SelectorKeyFlags
defaultRSA 1024 bits
dkimRSA 3072 bits
selector1RSA 2048 bits

Checks

  • ✓ Keys found: default, dkim, selector1 #7
    DKIM keys found for this domain with selectors: default, dkim, selector1
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: default (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
10deutschefamilienversicherung-de02b.mail.protection.outlook.comA 52.101.170.0 A 52.101.170.1 A 52.101.170.2 A 52.101.168.0 AAAA 2a01:111:f403:ca2d::1 AAAA 2a01:111:f403:ca2d:: AAAA 2a01:111:f403:ca2d::2 AAAA 2a01:111:f403:ca27::mail-fr5p281cu00500.inbound.protection.outlook.com ✓ mail-fr4p281cu03101.inbound.protection.outlook.com ✓ mail-fr6p281cu00202.inbound.protection.outlook.com ✓ mail-beup281cu00100.inbound.protection.outlook.com ✓ mail-fr4p281cu03101.inbound.protection.outlook.com ✓ mail-fr5p281cu00500.inbound.protection.outlook.com ✓ mail-fr6p281cu00202.inbound.protection.outlook.com ✓ mail-beup281cu00100.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
deutschefamilienversicherung-de02b.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