launchpad.net

launchpad.net · Last checked 2026-10-04 02:07 UTC

launchpad.net

Needs work, with 2 things to fix

launchpad.net scored 65/100 (grade C). The main issues are DMARC policy is none and no DKIM key found for the common selectors, plus 1 more.

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

2 passed2 need attention0 failing4 for information
Fix this firstThe change with the biggest effect

Strengthen the DMARC policy

Quarantines 25% of mail that fails DMARC, a safe first step: check the reports for legitimate senders that fail before going further.

TypeTXT
Name / Host
_dmarc.launchpad.net

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-rua+launchpad@admin.canonical.com; adkim=r; aspf=r
Replaces
v=DMARC1; p=none; pct=100; rua=mailto:dmarc-rua+launchpad@admin.canonical.com

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?Only one MX hostInfo
  • Info: Only one MX host

    All mail for launchpad.net goes to mx.launchpad.net. Most hosted providers make that one name highly available; if you run your own server, consider a backup MX.

SPFWho may send as you?No issues foundPass

Nothing to report.

DKIMAre your emails signed?No DKIM key found for the common selectorsNeeds attention
  • Warning: No DKIM key found for the common selectors

    None of the 47 selectors probed under launchpad.net publish a DKIM key. DNS cannot list selectors, so a key under a custom selector may exist: find the s= value in the DKIM-Signature header of a message you sent and check that selector. If DKIM is not set up, enable it at each service that sends mail for launchpad.net.

DMARCWhat happens to fakes?DMARC policy is noneNeeds attention
  • Warning: DMARC policy is none

    A none policy only monitors: mail that fails DMARC is still delivered, so anyone can spoof the domain. Once reports show your legitimate senders pass, move to quarantine and then reject.

    How to fix this
  • Warning: External DMARC report address is not authorized

    Reports go to admin.canonical.com, which is outside launchpad.net. RFC 7489 requires that domain to publish a valid v=DMARC1 TXT record at launchpad.net._report._dmarc.admin.canonical.com; without it receivers will not send you aggregate reports. Your report provider normally publishes this for you.

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.launchpad.net. 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.launchpad.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.launchpad.net. 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 launchpad.net publishes an MTA-STS policy at https://mta-sts.launchpad.net/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT
Name / Host
_mta-sts.launchpad.net

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

Value
v=STSv1; id=202610040207

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.launchpad.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.launchpad.net/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: mx.launchpad.net
max_age: 604800

Set up a TLS report addressinstruction

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

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

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