pcspezialist.de

Checked 21 October 2026, 23:42 UTC · via 8.8.8.8
!Passed with warnings
32 passed 1 warning 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.google.com ~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

warn

p=reject (_dmarc.pcspezialist.de)

Found

Record
v=DMARC1; p=reject; pct=100; rua=mailto:re+kstqzkwg1lk@dmarc.postmarkapp.com,mailto:dmarc_agg@vali.email; ruf=mailto:stefan.beining+forensic-reports@synaxon.de; adkim=r; aspf=r; fo=0;
Found at
_dmarc.pcspezialist.de
External report address
mailto:re+kstqzkwg1lk@dmarc.postmarkapp.com (authorized)
External report address
mailto:dmarc_agg@vali.email (authorized)
External report address
mailto:stefan.beining+forensic-reports@synaxon.de (not authorized)
TagValueMeaning
vDMARC1Version
prejectPolicy
pct100Percentage of mail the policy applies to
ruamailto:re+kstqzkwg1lk@dmarc.postmarkapp.com,mailto:dmarc_agg@vali.emailAggregate report addresses
rufmailto:stefan.beining+forensic-reports@synaxon.deFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo0Failure reporting options

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ 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:re+kstqzkwg1lk@dmarc.postmarkapp.com, mailto:dmarc_agg@vali.email
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • !
    Report address not authorized
    These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:stefan.beining+forensic-reports@synaxon.de (needs pcspezialist.de._report._dmarc.synaxon.de). Ask the report provider to publish the record, or check the address.
    #29

DKIM

pass

Selectors: google

Found

Selectors
google
_domainkey
NOERROR
SelectorKeyFlags
googleRSA 2048 bits

Checks

  • ✓ Keys found: google #7
    DKIM keys found for this domain with selectors: google
  • ✓ Strong keys #23
    DKIM keys are strong enough: google: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
60897, 40898
Signatures valid until
19 November 2026, 07:11 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-11-19 #21
    DNSKEY signatures are valid until 2026-11-19T07:11:14Z.

MX

pass

5 mail servers

Found

PriorityHostRecordsReverse DNS
1aspmx.l.google.comA 142.251.127.26 AAAA 2a00:1450:4001:c21::1alcfrai-in-f26.1e100.net ✓ lcfrai-in-f26.1e100.net ✓
5alt1.aspmx.l.google.comA 142.250.147.27 AAAA 2a00:1450:4025:c01::1ard-in-f27.1e100.net ✓ rd-in-f26.1e100.net ✓
5alt2.aspmx.l.google.comA 172.253.152.26 AAAA 2a00:1450:4010:c22::1ayulpptr-in-f26.1e100.net ✓ yulpptr-in-f26.1e100.net ✓
10alt3.aspmx.l.google.comA 192.179.20.26 AAAA 2404:6800:4000:1027::1ancboms-in-f26.1e100.net ✓ ncboms-in-f26.1e100.net ✓
10alt4.aspmx.l.google.comA 192.178.158.26 AAAA 2404:6800:4013:813::1blcdels-in-f26.1e100.net ✓ lcdels-in-f27.1e100.net ✓

Checks

  • ✓ 5 MX records #9
    Found 5 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 5 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 5 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 10 MX addresss have a PTR record that resolves back to them.

TLS

info

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

Found

MTA-STS record
v=STSv1;id=202603121156;
Policy URL
https://mta-sts.pcspezialist.de/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com
Max age
2592000 seconds
TLS-RPT record
v=TLSRPTv1;rua=mailto:admin+pcspezialist.de@synaxon.com;

DANE (TLSA records)

MX hostTLSADNSSEC
aspmx.l.google.comnone-
alt1.aspmx.l.google.comnone-
alt2.aspmx.l.google.comnone-
alt3.aspmx.l.google.comnone-
alt4.aspmx.l.google.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 202603121156.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 720h0m0s.
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: mailto:admin+pcspezialist.de@synaxon.com
  • 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