steampowered.com

steampowered.com · Last checked 2026-10-04 02:07 UTC

steampowered.com

Excellent, with 1 thing to fix

steampowered.com scored 92/100 (grade A). The main issue is DKIM key shorter than 2048 bits.

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

3 passed1 needs attention0 failing4 for information

All checks

MXCan servers find your inbox?Only one MX hostInfo
  • Info: Only one MX host

    All mail for steampowered.com goes to smtp.steampowered.com. 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?DKIM key shorter than 2048 bitsNeeds attention
  • Warning: DKIM key shorter than 2048 bits

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

    steampowered.com publishes a DKIM key under smtp.

DMARCWhat happens to fakes?DMARC uses strict alignmentInfo
  • Info: DMARC uses strict alignment

    With adkim=s or aspf=s the DKIM d= domain or the bounce domain must equal the From domain exactly; a subdomain is not enough. Third-party senders that sign or bounce from a subdomain (or their own domain) will then fail DMARC unless they are configured to use your exact domain.

AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?No issues foundPass

Nothing to report.

MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
  • Info: No MTA-STS record

    No MTA-STS record at _mta-sts.steampowered.com. 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.steampowered.com. 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

Publish the MTA-STS recordTXT

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

TypeTXT
Name / Host
_mta-sts.steampowered.com

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.steampowered.com. 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.steampowered.com/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: smtp.steampowered.com
max_age: 604800

Set up a TLS report addressinstruction

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

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