asus.com
Good, with 2 things to fix
asus.com scored 76/100 (grade B). The main issues are DKIM key shorter than 2048 bits and no DMARC aggregate report address, plus 1 more. Detected senders: Microsoft 365.
Checked 2026-10-04 02:16 UTC · fresh check
Strengthen the DMARC policy
Rejects mail that fails DMARC, the strongest protection against spoofing. There is no report address yet: set one up first (see the DMARC reporting fix) so you can confirm your legitimate mail passes before enforcing. Changes: Subdomains move one step, from sp=quarantine to the domain policy (p=reject).
_dmarc.asus.com
Some DNS providers want just “_dmarc” here.
v=DMARC1; p=reject; adkim=r; aspf=r
v=DMARC1; p=reject; pct=100; sp=quarantine
How to apply it
- Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
- Find the existing TXT record with that name and replace its value.
- 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 issues foundPass
Nothing to report.
DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention
- Warning: DKIM key shorter than 2048 bits
s2 (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
asus.com publishes a DKIM key under s1, s2.
DMARCWhat happens to fakes?Subdomain policy is weaker than the domain policyNeeds attention
- Warning: Subdomain policy is weaker than the domain policy
sp=quarantine is weaker than p=reject, so attackers can spoof any subdomain of asus.com (for example billing.asus.com) even though the main domain is protected.
How to fix this - Warning: No DMARC aggregate report address
Without a rua address you receive no aggregate reports, so you cannot see who sends as your domain or safely tighten the policy.
How to fix this
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.asus.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.asus.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
Other fixes
Set up a DMARC report addressinstruction
Without a rua address nobody receives aggregate reports, so you cannot see who sends as asus.com or tell when it is safe to tighten the policy. Adding reporting does not change how receivers treat your mail.
Applies to: _dmarc.asus.com
- Get an address that collects DMARC aggregate reports: add asus.com to MailVakt to receive one, or sign up with any DMARC report service. 2. Edit the TXT record at _dmarc.asus.com and add rua=mailto:<that address>, keeping every other tag (p=reject, sp=quarantine) as it is. 3. A report service on another domain must authorize asus.com; most publish that record for you.
Publish the MTA-STS recordTXT
Tells sending servers that asus.com publishes an MTA-STS policy at https://mta-sts.asus.com/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.asus.com
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040216
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.asus.com. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.
https://mta-sts.asus.com/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: mg.asus.com mx: mg1.asus.com mx: mg2.asus.com max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to asus.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.asus.com
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@asus.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.asus.com with the value v=TLSRPTv1; rua=mailto:<that address>.