maritim.de

Checked 21 October 2026, 23:21 UTC · via 8.8.8.8
✗Problems found
26 passed 3 warnings 1 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.salesforce.com include:spf.hornetsecurity.com include:spf-de.emailsignatures365.com include:relaysrv1.pegswebservices.com include:spf.teuto.net include:spf.dvinci.de include:spf.protection.outlook.com include:_spf.customer.avenit.de include:_spf.travelclick.com ~all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; pct=100; rua=mailto:a.0muzu0ts@reports.hornetdmarc.com
Found at
_dmarc.maritim.de
External report address
mailto:a.0muzu0ts@reports.hornetdmarc.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:a.0muzu0ts@reports.hornetdmarc.comAggregate report addresses

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:a.0muzu0ts@reports.hornetdmarc.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: default, selector1

Found

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

Checks

  • ✓ Keys found: default, selector1 #7
    DKIM keys found for this domain with selectors: default, 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

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
24104, 52535
Signatures valid until
2 November 2026, 00:31 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-11-02 #21
    DNSKEY signatures are valid until 2026-11-02T00:31:14Z.

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
30mx01.hornetsecurity.comA 94.100.132.8mx01.hornetsecurity.com ✓
40mx02.hornetsecurity.comA 94.100.136.8mx02.hornetsecurity.com ✓
50mx03.hornetsecurity.comA 94.100.134.8mx03.hornetsecurity.com ✓
60mx04.hornetsecurity.comA 94.100.136.7mx04.hornetsecurity.com ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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: mx01.hornetsecurity.com, mx02.hornetsecurity.com, mx03.hornetsecurity.com, mx04.hornetsecurity.com
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 4 MX addresss have a PTR record that resolves back to them.

TLS

warn

MTA-STS none · TLS-RPT · DANE on 0 of 4 MX hosts

Found

MTA-STS record
v=STSv1; id=20260506
Policy URL
https://mta-sts.maritim.de/.well-known/mta-sts.txt
Mode
none
Allowed MX
mx1.teuto.net, mx2.teuto.net
Max age
86400 seconds
TLS-RPT record
v=TLSRPTv1;rua=mailto:mta-sts-reports@teuto.net

DANE (TLSA records)

MX hostTLSADNSSEC
mx01.hornetsecurity.comnone-
mx02.hornetsecurity.comnone-
mx03.hornetsecurity.comnone-
mx04.hornetsecurity.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20260506.
  • !
    Policy disabled (mode: none)
    The MTA-STS policy is switched off with mode: none.
    #33
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:mta-sts-reports@teuto.net
  • 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