visualstudio.com

visualstudio.com · Last checked 2026-10-04 02:12 UTC

visualstudio.com

Poor, with 5 things to fix

visualstudio.com scored 50/100 (grade D). The main issues are no DMARC record and no DKIM key found for the common selectors, plus 5 more.

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

1 passed4 need attention1 failing2 for information

Diagnosis notes

  • Warning: DNS lookup budget exhausted

    This diagnosis stopped sending DNS queries after 150 queries. Checks that needed more lookups report their remaining results as unknown; the domain's records may be unusually large or slow to answer.

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 visualstudio.com before enforcing a policy. Move to quarantine once the reports show only your own services.

TypeTXT
Name / Host
_dmarc.visualstudio.com

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

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

Nothing to report.

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 visualstudio.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 visualstudio.com.

  • Warning: Some DKIM lookups failed

    24 of 47 selector lookups under visualstudio.com returned TIMEOUT, so whether those selectors hold a key is unknown. Try again later; if it persists, check the domain's nameservers.

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

    There is no v=DMARC1 TXT record at _dmarc.visualstudio.com. 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?SPF alignment is unknownInfo
  • Info: SPF alignment is unknown

    The SPF record of visualstudio.com authorizes no sender (no +ip4, +ip6, +a, +mx, +exists or +ptr term, include of a record that has one, or +all before all), so SPF never passes and cannot align. That is correct for a domain that sends no mail; otherwise DMARC depends on DKIM alone.

BIMICan inboxes show your logo?Could not look up the BIMI recordNeeds attention
  • Warning: Could not look up the BIMI record

    The TXT query for default._bimi.visualstudio.com returned TIMEOUT, so BIMI status is unknown. Try again later.

MTA-STSIs mail to you encrypted?Could not look up the MTA-STS recordNeeds attention
  • Warning: Could not look up the MTA-STS record

    The TXT query for _mta-sts.visualstudio.com returned TIMEOUT, so MTA-STS status is unknown. Try again later.

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

    No TLS reporting record at _smtp._tls.visualstudio.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 TLS report addressinstruction

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

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