hwk-hamburg.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 mx a ip4:52.157.149.216/32 ip4:37.61.205.11/32 ip4:195.145.241.100/32 include:spf.protection.artware.at include:spf.emailsys.net ~all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1;p=none;rua=mailto:DMARC-Monitoring@hwk-hamburg.de;ruf=mailto:DMARC-Monitoring@hwk-hamburg.de;fo=1
Found at
_dmarc.hwk-hamburg.de
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:DMARC-Monitoring@hwk-hamburg.deAggregate report addresses
rufmailto:DMARC-Monitoring@hwk-hamburg.deFailure report addresses
fo1Failure reporting options

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:DMARC-Monitoring@hwk-hamburg.de
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10post01.hwk-hamburg.deA 193.158.6.82post01.hwk-hamburg.de ✓
10post02.hwk-hamburg.deA 195.145.241.82post02.hwk-hamburg.de ✓

Checks

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

TLS

warn

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

Found

MTA-STS record
v=STSv1; id=2025050501;
Policy URL
https://mta-sts.hwk-hamburg.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
post01.hwk-hamburg.de, post02.hwk-hamburg.de
Max age
2419200 seconds

DANE (TLSA records)

MX hostTLSADNSSEC
post01.hwk-hamburg.denone-
post02.hwk-hamburg.denone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 2025050501.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 672h0m0s.
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #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