onelink.me

onelink.me · Last checked 2026-10-04 02:08 UTC

onelink.me

Poor, with 3 things to fix

onelink.me scored 50/100 (grade D). The main issues are no DMARC record and no DKIM key found for the common selectors, plus 1 more. Detected senders: Google Workspace.

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

1 passed2 need attention1 failing4 for informationDetected senders: Google Workspace
Fix this firstThe change with the biggest effect

Publish a DMARC record

Starts DMARC in monitoring mode (p=none), so you can see who sends as onelink.me before enforcing a policy. Move to quarantine once the reports show only your own services.

TypeTXT
Name / Host
_dmarc.onelink.me

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=none; adkim=r; aspf=r

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. Add a new TXT record with the name and value above.
  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?Mail relies on implicit A recordNeeds attention
  • Warning: Mail relies on implicit A record

    onelink.me has no MX records, so senders fall back to its A/AAAA address (RFC 5321 implicit MX). Publish an explicit MX record, or a null MX ("0 .") if the domain should not receive mail.

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?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 onelink.me 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 onelink.me.

DMARCWhat happens to fakes?No DMARC recordFailing
  • Fail: No DMARC record

    There is no v=DMARC1 TXT record at _dmarc.onelink.me. Without DMARC, receivers have no policy for mail that fails SPF and DKIM, and Gmail and Yahoo require one for bulk senders. Start with p=none and a rua address to collect reports.

    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.onelink.me. 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.onelink.me. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.

TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
  • Info: No TLS-RPT record

    No TLS reporting record at _smtp._tls.onelink.me. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

Other fixes

Enable DKIM for Google Workspaceinstruction

Google Workspace generates the DKIM key for each account, so the exact record must come from Google Workspace. Without DKIM, mail it sends for onelink.me cannot pass DMARC through DKIM.

Applies to: google._domainkey.onelink.me

  1. In Google Workspace, enable DKIM signing for onelink.me: Generate the key in Admin console > Apps > Gmail > Authenticate email, then publish the TXT record shown there. Publish exactly the record Google Workspace shows (TXT or CNAME) at the host name it gives, then turn signing on. Instructions: https://support.google.com/a/answer/174124

Set up a TLS report addressinstruction

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

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

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