Is dotnet.microsoft.com safe to use as a vendor?

dotnet.microsoft.com scored 92/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 11 checks passed, 4 warnings, 0 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does dotnet.microsoft.com use?

dotnet.microsoft.com uses TLSv1.3 with TLS_AES_256_GCM_SHA384. TLSv1.3 negotiated with TLS_AES_256_GCM_SHA384 (256-bit). Strong configuration with no deprecated protocols or weak ciphers detected.

Does dotnet.microsoft.com have DMARC configured?

Yes. dotnet.microsoft.com's DMARC policy is set to 'reject'. SPF record: yes. Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 5/10 (within limit); DKIM configured (selectors: selector2, s1024).

Does dotnet.microsoft.com have SPF configured?

Yes. SPF record found: v=spf1 include:_spf-a.microsoft.com include:_spf-b.microsoft.com include:_spf-c....

Does dotnet.microsoft.com have security headers configured?

dotnet.microsoft.com has 3 of 5 recommended security headers. Present: CSP, X-Content-Type-Options, X-Frame-Options. Missing: Referrer-Policy, Permissions-Policy.

Does dotnet.microsoft.com use HSTS?

Yes. HSTS enabled: max-age=31536000s (365 days) with includeSubDomains and preload. Meets best-practice configuration.

Has dotnet.microsoft.com been involved in a data breach?

No known breaches found. No known breaches found in public disclosure databases.

Does dotnet.microsoft.com have known CVE vulnerabilities?

Detected technologies: ASP.NET. No version information exposed — CVE matching not possible (this is good practice).

Is dotnet.microsoft.com's SSL certificate valid?

Yes. Strengths: Certificate valid, 96 days remaining; Issued by Microsoft Corporation; 148 certificates logged in CT; Certificates from 2 CAs: "DigiCert, Microsoft Corporation.

dotnet.microsoft.com Security Report — Grade A- (92/100)

Q: Does dotnet.microsoft.com have DNSSEC enabled?

No. Strengths: 4 nameservers configured (ns2-39.azure-dns.net, ns3-39.azure-dns.org, ns4-39.azure-dns.info, ns1-39.azure-dns.com); NS records span 4 providers (azure-dns.net, azure-dns.org, azure-dns.info, azure-dns.com) — genuine redundancy; SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s), 1 AAAA record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

A-

Trust rating

Excellent · 92/100

Procurement snapshot

No critical findings. The 4 remaining items are configuration gaps, not architectural problems.

Strengths

MX Records & Mail Provider

DMARC / Email Security

TLS Configuration

TLS Protocol Support

Questions to ask

Confirm DNSSEC rollout timeline

Estimated remediation effort: 1–3 days

Based on a passive external scan — supplement with vendor-provided attestations, not a replacement.

Trust Score Trend

→ No change 1 scan · Last scanned October 15, 2026

Score

100 75 50 25 0

A-

dotnet.microsoft.com

92/100

Compliance & Certifications

Not yet verified

SOC 2 Type II

Audit report not on file

3rd party · AICPA

ISO 27001

Certificate not on file

3rd party · accredited body

GDPR

DPA not on file

Self-reported

CCPA

Self-reported

Incident History

No public breaches on record

Security Posture

4 items need attention

11 passed

Turn on DNSSEC for your domain

DNS Configuration

1–3 days (mostly waiting, not active work) Medium

This allows an attacker to silently redirect your visitors to a fake site. DNSSEC is a signature system that stops attackers from forging DNS answers — without it, someone could redirect visitors of dotnet.microsoft.com to a fake site without them noticing. Turning it on takes coordination between your DNS provider and your domain registrar, but it's a one-time setup.

NIST 800-53SC-20

Secure name/address resolution service

How to fix this

1Check whether your DNS provider supports DNSSEC in your Azure DNS DNS dashboard (https://learn.microsoft.com/azure/dns/dns-getstarted-portal) — most major ones do (Cloudflare, Route53, GoDaddy, Namecheap).

2Turn on DNSSEC signing there — it will generate a DS record for you.

3Copy that DS record into your domain registrar's DNSSEC settings for the .com domain.

4Confirm it worked: search "dnssec checker" and enter dotnet.microsoft.com.

DNSSEC guide

Report unlocked.

View all 11 passed checks

MX Records & Mail Provider

DMARC / Email Security

TLS Configuration

TLS Protocol Support

MTA-STS & TLS Reporting

Known Breaches

HSTS Header

Cookie Security

Subprocessors & Tech Stack

CVE Exposure

Certificate Hygiene

Couldn't check: Malware / Phishing Blocklist — the check didn't complete (the site blocked or timed out our scanner, or a data source was unavailable), so this isn't counted in the score.

Company Signals

Operational risk

Last funding

Employees

Trust Resources

Claim profile →

Trust Center

Not detected

DPA (Data Processing Agreement)

Subprocessors List

Similar companies

Appears in

Vendors graded A

378 companies · LynxRadar ranking

Top 10% by security score

288 companies · LynxRadar ranking

Medium Priority

Not enabled

Strengths: 4 nameservers configured (ns2-39.azure-dns.net, ns3-39.azure-dns.org, ns4-39.azure-dns.info, ns1-39.azure-dns.com); NS records span 4 providers (azure-dns.net, azure-dns.org, azure-dns.info, azure-dns.com) — genuine redundancy; SOA record present and MNAME consistent with NS set; 1 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s), 1 AAAA record(s). Issues: DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

Warn

Strengths: CAA records configured at microsoft.com (1 record(s)); Additional tags present: contactemail. Issues: No iodef record — CA violations won't be reported to the domain owner.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆

3/5 present

Missing: Referrer-Policy, Permissions-Policy

Likelihood: ★★☆☆☆

Impact: ★☆☆☆☆

Warn

No security.txt found. Publishing a security.txt at /.well-known/security.txt is the industry standard (RFC 9116) for vulnerability disclosure policies. Its absence may indicate a less mature security program.

Likelihood: ★☆☆☆☆

Impact: ★☆☆☆☆