steamstatic.com

steamstatic.com · Last checked 2026-10-04 02:17 UTC

steamstatic.com

Needs work, with 3 things to fix

steamstatic.com scored 72/100 (grade C). The main issues are no DKIM key found for the common selectors and DMARC alignment: DKIM alignment is unlikely under adkim=s, plus 1 more.

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

1 passed3 need attention0 failing4 for information
Fix this firstThe change with the biggest effect

Reduce SPF DNS lookups

Evaluating SPF for steamstatic.com takes 10 DNS lookups including nested includes; receivers stop at 10 and fail SPF. No detected sending service accounts for these includes; remove each one you no longer send through: _netblocks.mimecast.com.

TypeTXT
Name / Host
steamstatic.com

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

Value
v=spf1 mx include:_netblocks.mimecast.com -all
Replaces
v=spf1 mx include:_netblocks.mimecast.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. 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?SPF is close to the 10-lookup limitNeeds attention
  • Warning: SPF is close to the 10-lookup limit

    Evaluating the SPF record for steamstatic.com needs 10 of the 10 allowed DNS lookups. Adding one more service, or a provider growing its own record, will break SPF.

    How to fix this
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 steamstatic.com 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 steamstatic.com.

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?DKIM alignment is unlikely under adkim=sNeeds attention
  • Warning: DKIM alignment is unlikely under adkim=s

    This is a heuristic. No DKIM key was found at steamstatic.com under the selectors we probed, and adkim=s requires the signing d= domain to equal steamstatic.com exactly. If your mail is signed with a provider's domain or a subdomain, DKIM will not align. A key may exist under a selector we did not try; send a test message to confirm.

BIMICan inboxes show your logo?No BIMI recordInfo
  • Info: No BIMI record

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

TypeTXT
Name / Host
_mta-sts.steamstatic.com

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.steamstatic.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.steamstatic.com/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: us-smtp-inbound-1.mimecast.com
mx: us-smtp-inbound-2.mimecast.com
max_age: 604800

Set up a TLS report addressinstruction

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

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

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