amon.tech

amon.tech · Last checked 2026-10-04 02:07 UTC

amon.tech

At risk, with 4 things to fix

amon.tech scored 24/100 (grade F). The main issues are no DMARC record and no SPF record, plus 2 more. Detected senders: Google Workspace.

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

2 passed2 need attention2 failing2 for informationDetected senders: Google Workspace
Fix this firstThe change with the biggest effect

Publish an SPF record

Lists the sending services detected for amon.tech (Google Workspace) and rejects everything else. Add any other service that sends as amon.tech before publishing. Changes: Added include:_spf.google.com for Google Workspace.

TypeTXT
Name / Host
amon.tech

Some DNS providers want “@” here instead of the full domain.

Value
v=spf1 include:_spf.google.com -all

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?No issues foundPass

Nothing to report.

SPFWho may send as you?No SPF recordFailing
  • Fail: No SPF record

    amon.tech publishes no TXT record starting with "v=spf1", so receivers cannot tell which servers may send mail for it. Publish one SPF record listing every service that sends as amon.tech.

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

    google (1024-bit), k1 (1024-bit), mail (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

    amon.tech publishes a DKIM key under google, k1, mail.

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

    There is no v=DMARC1 TXT record at _dmarc.amon.tech. 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?BIMI logo is unreachableNeeds attention
  • Warning: BIMI logo is unreachable

    The SVG at https://amon.tech/assets/images/mobile-step-image/svg/amn.svg could not be fetched (HTTP 526). 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.amon.tech. 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.amon.tech. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

Other fixes

Publish a DMARC recordTXT

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

TypeTXT
Name / Host
_dmarc.amon.tech

Some DNS providers want just “_dmarc” here.

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

Publish the MTA-STS recordTXT

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

TypeTXT
Name / Host
_mta-sts.amon.tech

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.amon.tech. 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.amon.tech/.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 amon.tech, 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.amon.tech

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