gtz.de

Checked 21 October 2026, 22:41 UTC · via 8.8.8.8
!Passed with warnings
28 passed 4 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.protection.outlook.com ip4:193.97.169.16/28 -all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1;p=reject;sp=reject;rua=mailto:giz.rua@emailsecurity.merox.io,mailto:dmarc-aggregate@giz.de
Found at
_dmarc.gtz.de
External report address
mailto:giz.rua@emailsecurity.merox.io (authorized)
External report address
mailto:dmarc-aggregate@giz.de (not authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
ruamailto:giz.rua@emailsecurity.merox.io,mailto:dmarc-aggregate@giz.deAggregate 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:giz.rua@emailsecurity.merox.io, mailto:dmarc-aggregate@giz.de
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • !
    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:dmarc-aggregate@giz.de (needs gtz.de._report._dmarc.giz.de). Ask the report provider to publish the record, or check the address.
    #29

DKIM

pass

Selectors: selector1, selector2

Found

Selectors
selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, selector2 #7
    DKIM keys found for this domain with selectors: selector1, selector2
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits.
  • ✓ 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
0gtz-de.mail.protection.outlook.comA 52.101.209.153 A 52.101.103.137 A 52.101.73.126 A 52.101.68.27mail-cpjpr04cu00101.inbound.protection.outlook.com ✓ mail-miypr02cu00101.inbound.protection.outlook.com ✓ mail-am8pr83cu00106.inbound.protection.outlook.com ✓ mail-db7pr03cu00503.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.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: gtz-de.mail.protection.outlook.com
    #11
  • !
    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 4 MX addresss have a PTR record that resolves back to them.

TLS

info

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

Found

MTA-STS record
v=STSv1; id=20250224
Policy URL
https://mta-sts.gtz.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
*.mail.protection.outlook.com
Max age
604800 seconds
TLS-RPT record
v=TLSRPTv1; rua=mailto:stsreports@giz.de,mailto:giz.tlsr@emailsecurity.merox.io

DANE (TLSA records)

MX hostTLSADNSSEC
gtz-de.mail.protection.outlook.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20250224.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 168h0m0s.
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:stsreports@giz.de, mailto:giz.tlsr@emailsecurity.merox.io
  • 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