fc-heidenheim.de

Checked 21 October 2026, 22:20 UTC · via 8.8.8.8
✗Problems found
22 passed 6 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx include:spf.protection.outlook.com include:spf.fc-heidenheim-de.cloud.nospamproxy.com include:spf.crsend.com a:mx4.eventim.de a:vega.graustich.com ip4:193.197.147.200 ip4:91.26.233.10 -all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; rua=mailto:ML-DMARC@fc-heidenheim.de; ruf=mailto:ML-DMARC@fc-heidenheim.de; fo=1; pct=60;
Found at
_dmarc.fc-heidenheim.de
TagValueMeaning
vDMARC1Version
pnonePolicy
pct60Percentage of mail the policy applies to
ruamailto:ML-DMARC@fc-heidenheim.deAggregate report addresses
rufmailto:ML-DMARC@fc-heidenheim.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:ML-DMARC@fc-heidenheim.de
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: selector1

Found

Selectors
selector1
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 1024 bits

Checks

  • ✓ Keys found: selector1 #7
    DKIM keys found for this domain with selectors: selector1
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (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

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
10fc-heidenheim-de.mail.cloud.nospamproxy.comA 178.212.92.204 A 193.37.132.36de-s02-gw2.mail.cloud.nospamproxy.com ✓ de-s02-gw1.mail.cloud.nospamproxy.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: fc-heidenheim-de.mail.cloud.nospamproxy.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 2 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
fc-heidenheim-de.mail.cloud.nospamproxy.com3 1 1 7acc5ebfd159a58b… 3 1 1 15987f49fc954bba… 3 1 1 897f916ec02bfb38… 3 1 1 4a8ccc4c8ae3d658…Yes

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
  • !
    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
  • ✓ DANE on all MX hosts #36
    All 1 MX host publish DNSSEC-validated TLSA records.

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