iwkoeln.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 a:spf.mas.t-systems-service.com a:k60828.coveto.de include:spf.mailjet.com ip4:87.79.12.44 ip4:87.79.12.45 ip4:89.1.85.243 ip4:176.9.21.28 ip4:212.114.35.242 ip4:212.114.34.232 ip4:212.114.34.50 ip4:212.114.35.226 ip4:85.13.129.239 ip4:172.16.244.130 ip4:87.79.12.40 ip4:172.16.244.15 ip4:79.142.32.16 ip4:85.13.144.213 include:sendgrid.net include:spf.protection.outlook.com include:spf.crsend.com include:_spf.recruiting-portal.com include:spf.orbit.teamleader.eu include:_spf.zimpel.de -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.iwkoeln.de)

Found

Record
v=DMARC1; p=none; pct=100; rua=mailto:c21a3e3fbe2748cea6d2f21daadcebf1@dmarc-reports.cloudflare.net,mailto:dmarc@iwkoeln.de; ruf=mailto:dmarc@iwkoeln.de; fo=1
Found at
_dmarc.iwkoeln.de
External report address
mailto:c21a3e3fbe2748cea6d2f21daadcebf1@dmarc-reports.cloudflare.net (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
pct100Percentage of mail the policy applies to
ruamailto:c21a3e3fbe2748cea6d2f21daadcebf1@dmarc-reports.cloudflare.net,mailto:dmarc@iwkoeln.deAggregate report addresses
rufmailto:dmarc@iwkoeln.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:c21a3e3fbe2748cea6d2f21daadcebf1@dmarc-reports.cloudflare.net, mailto:dmarc@iwkoeln.de
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

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

3 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.mas.t-systems-service.comA 217.150.155.10 A 217.150.155.12 A 46.29.101.2 A 46.29.101.1mgb-mta01.mas.t-systems-service.com ✓ mgb-mta02.mas.t-systems-service.com ✓ muc-mta02.mas.t-systems-service.com ✓ muc-mta01.mas.t-systems-service.com ✓
20mx2.mas.t-systems-service.comA 217.150.155.10 A 46.29.101.2 A 46.29.101.1 A 217.150.155.12mgb-mta01.mas.t-systems-service.com ✓ muc-mta02.mas.t-systems-service.com ✓ muc-mta01.mas.t-systems-service.com ✓ mgb-mta02.mas.t-systems-service.com ✓
30mx3.mas.t-systems-service.comA 94.100.254.155ffm-mta01.mas.t-systems-service.com ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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: mx1.mas.t-systems-service.com, mx2.mas.t-systems-service.com, mx3.mas.t-systems-service.com
    #11
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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 9 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx1.mas.t-systems-service.comnone-
mx2.mas.t-systems-service.comnone-
mx3.mas.t-systems-service.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