Good, with 3 things to fix

detectify.com scored 76/100 (grade B). The main issues are DKIM key shorter than 2048 bits and no DMARC aggregate report address, plus 1 more. Detected senders: Google Workspace.

Checked 2026-10-03 22:10 UTC

2 passed3 need attention0 failing3 for informationDetected senders: Google Workspace

Fix this firstThe change with the biggest effect

Set up a DMARC report address

Without a rua address nobody receives aggregate reports, so you cannot see who sends as detectify.com or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.

Applies to: _dmarc.detectify.com

Get an address that collects DMARC aggregate reports: add detectify.com to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.detectify.com and add rua=mailto:<that address>, keeping every other tag (p=reject, sp=reject) as it is. 3. A report service on another domain must authorize detectify.com; most publish that record for you.

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?SPF record is very longNeeds attention

Warning: SPF record is very long
The SPF record is 2187 characters. Long TXT answers can exceed the 512-byte UDP limit and force fallback to TCP, which some receivers do not do. Replace individual IP ranges with includes or ranges, or remove services you no longer use. (Only the total length is checked: the resolver returns the record already joined, so the 255-character limit on each individual string cannot be seen here.)
Info: SPF ends in softfail (~all)
"~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.

DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention

Warning: DKIM key shorter than 2048 bits
google (1024-bit), k1 (1024-bit) uses an RSA key below 2048 bits. Short keys can be factored and some receivers treat them as weak. Rotate to a 2048-bit key at your sending provider.
Pass: DKIM key published
detectify.com publishes a DKIM key under google, k1, s1, s2.

DMARCWhat happens to fakes?No DMARC aggregate report addressNeeds attention

Warning: No DMARC aggregate report address
Without a rua address you receive no aggregate reports, so you cannot see who sends as your domain or safely tighten the policy.
How to fix this

AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?No BIMI recordInfo

Info: No BIMI record
No BIMI record at default._bimi.detectify.com. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.
How to fix this

MTA-STSIs mail to you encrypted?No MTA-STS recordInfo

Info: No MTA-STS record
No MTA-STS record at _mta-sts.detectify.com. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
How to fix this

TLS-RPTWill you hear about failures?No TLS-RPT recordInfo

Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.detectify.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this

Other fixes

Publish the MTA-STS recordTXT

Tells sending servers that detectify.com publishes an MTA-STS policy at https://mta-sts.detectify.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT

Name / Host

_mta-sts.detectify.com

Some DNS providers want just “_mta-sts” here.

Value

v=STSv1; id=202610032210

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.detectify.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location

https://mta-sts.detectify.com/.well-known/mta-sts.txt

Contents

version: STSv1
mode: testing
mx: aspmx.l.google.com
mx: alt1.aspmx.l.google.com
mx: alt2.aspmx.l.google.com
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to detectify.com, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.

Applies to: _smtp._tls.detectify.com

Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@detectify.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.detectify.com with the value v=TLSRPTv1; rua=mailto:<that address>.

Prepare BIMIinstruction

BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.

Applies to: default._bimi.detectify.com

Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://detectify.com/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.detectify.com with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.