networkadvertising.org

networkadvertising.org · Last checked 2026-10-04 02:17 UTC

networkadvertising.org

Good, with 2 things to fix

networkadvertising.org scored 84/100 (grade B). The main issues are DKIM key shorter than 2048 bits and DMARC policy applies to only 10% of mail. Detected senders: Google Workspace, Amazon SES and HubSpot.

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

3 passed2 need attention0 failing3 for informationDetected senders: Google Workspace, Amazon SES, HubSpot
Fix this firstThe change with the biggest effect

Strengthen the DMARC policy

Quarantines all mail that fails DMARC. Move on to reject once the reports stay clean.

TypeTXT
Name / Host
_dmarc.networkadvertising.org

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=quarantine; rua=mailto:dmarc_agg@vali.email; adkim=r; aspf=r
Replaces
v=DMARC1;p=quarantine;pct=10;rua=mailto:dmarc_agg@vali.email;

How to apply it

  1. Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
  2. Find the existing TXT record with that name and replace its value.
  3. Save, then come back and re-check. DNS changes can take up to a few hours to show.

All checks

MXCan servers find your inbox?No issues foundPass

Nothing to report.

SPFWho may send as you?No issues foundPass

Nothing to report.

DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention
  • Warning: DKIM key shorter than 2048 bits

    google (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

    networkadvertising.org publishes a DKIM key under google.

DMARCWhat happens to fakes?DMARC policy applies to only 10% of mailNeeds attention
  • Warning: DMARC policy applies to only 10% of mail

    pct=10 means the remaining 90% of failing mail is treated one step more leniently. Raise pct to 100 when you are confident.

    How to fix this
  • 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?No BIMI recordInfo
  • Info: No BIMI record

    No BIMI record at default._bimi.networkadvertising.org. 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.networkadvertising.org. 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.networkadvertising.org. 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 networkadvertising.org publishes an MTA-STS policy at https://mta-sts.networkadvertising.org/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT
Name / Host
_mta-sts.networkadvertising.org

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

Value
v=STSv1; id=202610040217

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.networkadvertising.org. 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.networkadvertising.org/.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: aspmx2.googlemail.com
mx: aspmx3.googlemail.com
max_age: 604800

Set up a TLS report addressinstruction

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

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@networkadvertising.org, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.networkadvertising.org 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.networkadvertising.org

  1. 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://networkadvertising.org/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.networkadvertising.org with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.