ameos.de

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

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.pironet-ndh.com ip4:62.12.146.162 ip4:195.227.214.234 ip4:195.227.214.230 ip4:195.227.214.233 ip4:62.55.182.68 ip4:80.252.97.80 ip4:213.20.233.11 ip4:213.20.233.13 ip4:212.111.227.113 ip4:87.230.34.142 ip4:82.198.223.81 ip4:82.198.223.82 ip4:80.228.249.68 ip4:193.242.121.220 ip4:193.242.121.221 ip4:193.242.121.222 ip4:5.10.180.85 ip4:23.88.40.61 ip6:2002:c3e3:33f7::c3e3:33f7 ip6:2002:c3e3:33f8::c3e3:33f8 ip6:2a01:4f8:c013:6be3::2 ip6:2002:c3e3:33f9::c3e3:33f9 ip6:2a01:4f8:10b:1514::102 mx -all
DNS lookups
2 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none;
Found at
_dmarc.ameos.de
TagValueMeaning
vDMARC1Version
pnonePolicy

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19

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

4 mail servers

Found

PriorityHostRecordsReverse DNS
10secure-mail01.de.cancom-mase.comA 195.227.216.2 AAAA 2001:1440:0:4036::11secure-mail01.de.cancom-mase.com ✓ no PTR
10secure-mail02.de.cancom-mase.comA 195.227.216.10 AAAA 2001:1440:0:4036::12secure-mail02.de.cancom-mase.com ✓ no PTR
20secure-mail03.de.cancom-mase.comA 195.227.138.21 AAAA 2001:1440:0:4036::13secure-mail03.de.cancom-mase.com ✓ no PTR
20secure-mail04.de.cancom-mase.comA 195.227.138.22 AAAA 2001:1440:0:4036::14secure-mail04.de.cancom-mase.com ✓ no PTR

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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 2001:1440:0:4036::11 (secure-mail01.de.cancom-mase.com), 2001:1440:0:4036::12 (secure-mail02.de.cancom-mase.com), 2001:1440:0:4036::13 (secure-mail03.de.cancom-mase.com), 2001:1440:0:4036::14 (secure-mail04.de.cancom-mase.com). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
secure-mail01.de.cancom-mase.com3 0 1 c16eaaae0ba9d414…Yes
secure-mail02.de.cancom-mase.com3 0 1 c16eaaae0ba9d414…Yes
secure-mail03.de.cancom-mase.com3 0 1 c16eaaae0ba9d414…Yes
secure-mail04.de.cancom-mase.com3 0 1 c16eaaae0ba9d414…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 4 MX hosts 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