netcologne.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:89.1.8.0/23 ip6:2001:4dd0:100::/48 ip4:194.8.194.0/24 ip4:81.173.193.0/24 ip4:81.173.194.0/26 ip4:81.173.246.0/24 ip4:185.98.184.0/24 ip4:80.82.206.0/26 ip4:46.228.134.9/32 ip4:62.146.4.26/32 include:spf.pressfile.de ~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

fail

p=none (_dmarc.netcologne.de)

Found

Record
v=DMARC1; p=none; sp=none; fo=1; adkim=r; aspf=r; ruf=mailto:dmarcfor@netcologne.de; rua=mailto:dmarcrec@netcologne.de
Found at
_dmarc.netcologne.de
TagValueMeaning
vDMARC1Version
pnonePolicy
spnoneSubdomain policy
ruamailto:dmarcrec@netcologne.deAggregate report addresses
rufmailto:dmarcfor@netcologne.deFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
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:dmarcrec@netcologne.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

pass

4 mail servers

Found

PriorityHostRecordsReverse DNS
10cc-mx1.netcologne.deA 89.1.8.141 AAAA 2001:4dd0:100:1062:25:3:0:1cc-mx1.netcologne.de ✓ cc-mx1.netcologne.de ✓
10cc-mx2.netcologne.deA 89.1.8.142 AAAA 2001:4dd0:100:1062:25:3:0:2cc-mx2.netcologne.de ✓ cc-mx2.netcologne.de ✓
10cc-mx3.netcologne.deA 89.1.8.143 AAAA 2001:4dd0:100:1062:25:3:0:3cc-mx3.netcologne.de ✓ cc-mx3.netcologne.de ✓
10cc-mx4.netcologne.deA 89.1.8.144 AAAA 2001:4dd0:100:1062:25:3:0:4cc-mx4.netcologne.de ✓ cc-mx4.netcologne.de ✓

Checks

  • ✓ 4 MX records #9
    Found 4 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.
  • ✓ 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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
cc-mx1.netcologne.denone-
cc-mx2.netcologne.denone-
cc-mx3.netcologne.denone-
cc-mx4.netcologne.denone-

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