mailingwork.de

Checked 21 October 2026, 23:21 UTC · via 8.8.8.8
!Passed with warnings
26 passed 5 warnings 0 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.mailingwork.de include:_spf_tools.mailingwork.de include:one.zoho.eu include:spf.zoho.eu include:eu.transmail.net include:_spf.google.com ~all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@mailingwork.de; pct=100; adkim=r; aspf=r
Found at
_dmarc.mailingwork.de
TagValueMeaning
vDMARC1Version
pquarantinePolicy
pct100Percentage of mail the policy applies to
ruamailto:dmarc-reports@mailingwork.deAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)

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-reports@mailingwork.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

pass

Selectors: selector1, selector2, google

Found

Selectors
selector1, selector2, google
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 2048 bits
googleRSA 2048 bits

Checks

  • ✓ Keys found: selector1, selector2, google #7
    DKIM keys found for this domain with selectors: selector1, selector2, google
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits; google: RSA 2048 bits.
  • ✓ 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
1smtp.google.comA 142.251.127.27 A 142.251.127.26 AAAA 2a00:1450:4001:c21::1b AAAA 2a00:1450:4001:c21::1alcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓ lcfrai-in-f27.1e100.net ✓ lcfrai-in-f26.1e100.net ✓

Checks

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

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
smtp.google.comnone-

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

warn

https://login.mailingwork.de/public/a_1354_hf9pW/webspace/CD-MAILINGWORK/Signet_blau_orange_tinyps.svg

Found

Record
v=BIMI1; l=https://login.mailingwork.de/public/a_1354_hf9pW/webspace/CD-MAILINGWORK/Signet_blau_orange_tinyps.svg; a=;
Found at
default._bimi.mailingwork.de
Logo
https://login.mailingwork.de/public/a_1354_hf9pW/webspace/CD-MAILINGWORK/Signet_blau_orange_tinyps.svg

Checks

  • !
    No certificate (a=)
    The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.
    #38
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.