Good, with 2 things to fix

pixiv.net scored 84/100 (grade B). The main issues are BIMI logo is unreachable and DKIM key shorter than 2048 bits. Detected senders: Google Workspace, SendGrid and Zendesk.

Checked 2026-10-04 02:20 UTC · fresh check

2 passed2 need attention0 failing4 for informationDetected senders: Google Workspace, SendGrid, Zendesk

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?SPF ends in softfail (~all)Info

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
s2 (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
pixiv.net publishes a DKIM key under s1, s2.

DMARCWhat happens to fakes?DMARC policy is quarantine; consider rejectInfo

Info: DMARC policy is quarantine; consider reject
Failing mail goes to spam rather than being refused. When reports show no legitimate failures, reject gives the strongest protection.
How to fix this

AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?BIMI logo is unreachableNeeds attention

Warning: BIMI logo is unreachable
The SVG at https://source.pixiv.net/special/bimi/pixiv-net-logo.svg could not be fetched (HTTP 403). Mailbox providers will not show the logo.

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

Info: No MTA-STS record
No MTA-STS record at _mta-sts.pixiv.net. 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.pixiv.net. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this

How to fix it

Strengthen the DMARC policyTXT

Rejects mail that fails DMARC, the strongest protection against spoofing.

TypeTXT

Name / Host

_dmarc.pixiv.net

Some DNS providers want just “_dmarc” here.

Value

v=DMARC1; p=reject; rua=mailto:174afb3d51494e64bee7d0913aea39b2@dmarc-reports.cloudflare.net,mailto:dmarc@pixiv.com; adkim=r; aspf=r

Replaces

v=DMARC1; p=quarantine; rua=mailto:174afb3d51494e64bee7d0913aea39b2@dmarc-reports.cloudflare.net,mailto:dmarc@pixiv.com; ruf=mailto:dmarc@pixiv.com; fo=1:d:s

Publish the MTA-STS recordTXT

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

TypeTXT

Name / Host

_mta-sts.pixiv.net

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

Value

v=STSv1; id=202610040220

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.pixiv.net. 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.pixiv.net/.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
mx: alt3.aspmx.l.google.com
mx: alt4.aspmx.l.google.com
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to pixiv.net, 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.pixiv.net

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