pkwteile.de

Checked 21 October 2026, 23:50 UTC · via 8.8.8.8
!Passed with warnings
23 passed 7 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:autodoc.dev ~all
DNS lookups
4 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1;p=quarantine;pct=100;aspf=r;adkim=r;fo=1;ri=86400;rua=mailto:dmarc-report@pkwteile.de
Found at
_dmarc.pkwteile.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:dmarc-report@pkwteile.deAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
ri86400Report interval (seconds)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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:dmarc-report@pkwteile.de
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: mail, k1

Found

Selectors
mail, k1
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 2048 bits
k1RSA 1024 bits

Checks

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

Signed, but no DS at parent

Found

DNSKEY records
Yes (2)
DS at parent
No
Algorithms
ECDSAP256SHA256 (13)
Key tags
2371, 34505
Signatures valid until
13 December 2026, 10:59 UTC

Checks

  • !
    Signed, but no DS at parent
    The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • ✓ Signatures valid until 2026-12-13 #21
    DNSKEY signatures are valid until 2026-12-13T10:59:38Z.

MX

warn

6 mail servers

Found

PriorityHostRecordsReverse DNS
5mailstream-eu1.mxrecord.ioA 172.65.245.214no PTR
10mailstream-central.mxrecord.mxA 172.65.64.78no PTR
10mx-02.autodoc.devA 46.4.242.226mx-02.autodoc.eu ✓
20mailstream-east.mxrecord.ioA 172.65.213.128no PTR
20mailstream-west.mxrecord.ioA 172.65.220.210no PTR
20mx-02.autodoc.devA 46.4.242.226mx-02.autodoc.eu ✓

Checks

  • ✓ 6 MX records #9
    Found 6 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: mailstream-eu1.mxrecord.io, mailstream-central.mxrecord.mx, mx-02.autodoc.dev, mailstream-east.mxrecord.io, mailstream-west.mxrecord.io, mx-02.autodoc.dev
    #11
  • ✓ Redundant MX hosts #12
    Found 6 MX records, which provides redundancy for email delivery.
  • !
    More than 5 MX records
    Found 6 MX records, which is more than the recommended maximum of 5. Too many MX records may indicate a misconfiguration.
    #13
  • ✓ 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: 172.65.245.214 (mailstream-eu1.mxrecord.io), 172.65.64.78 (mailstream-central.mxrecord.mx), 172.65.213.128 (mailstream-east.mxrecord.io), 172.65.220.210 (mailstream-west.mxrecord.io). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mailstream-eu1.mxrecord.ionone-
mailstream-central.mxrecord.mxnone-
mx-02.autodoc.devnone-
mailstream-east.mxrecord.ionone-
mailstream-west.mxrecord.ionone-

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