Is config.office.com safe to use as a vendor?

config.office.com scored 82/100 on LynxRadar's security posture assessment. The domain meets baseline security requirements. 10 checks passed, 3 warnings, 2 critical issues across 16 passive checks including TLS, DMARC, security headers, breaches, and CVEs.

What TLS version does config.office.com use?

config.office.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 config.office.com have SPF configured?

No. No SPF record found for config.office.com.

Does config.office.com have security headers configured?

config.office.com has 1 of 5 recommended security headers. Present: CSP. Missing: X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy.

Does config.office.com use HSTS?

Yes. HSTS enabled: max-age=31536000s (365 days). includeSubDomains present. Missing preload directive.

Has config.office.com been involved in a data breach?

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

Does config.office.com have known CVE vulnerabilities?

Detected technologies: Microsoft-HTTPAPI/2.0. No high or critical CVEs found for detected versions.

Is config.office.com's SSL certificate valid?

Yes. Strengths: Certificate valid, 167 days remaining; Issued by Microsoft Corporation; 1628 certificates logged in CT; Certificates from 2 CAs: DigiCert Inc, Microsoft Corporation.

Does config.office.com have DNSSEC enabled?

Yes. Strengths: 4 nameservers configured (ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info); NS records span 4 providers (azure-dns.com, azure-dns.net, azure-dns.org, azure-dns.info) — genuine redundancy; SOA record present and MNAME consistent with NS set; DNSSEC enabled: zone signed (DNSKEY present) and chain of trust intact (DS record in parent zone); Zone transfers properly restricted on all nameservers; Address records present: 1 A record(s), 1 AAAA record(s).

config.office.com Security Report — Grade B- (82/100)

Q: Does config.office.com have DMARC configured?

Yes. config.office.com's DMARC policy is set to 'quarantine'. SPF record: no. Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured. Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright; No SPF record found. Note: DKIM couldn't be confirmed from outside (custom selector names can't be looked up, and some DNS hosts don't expose them), so it isn't counted against the score.

B-

Trust rating

Good · 82/100

Procurement snapshot

0 critical findings identified — these point to architectural gaps, not just configuration tweaks.

Strengths

MX Records & Mail Provider

DNS Configuration

DNS CAA Records

TLS Configuration

Questions to ask

Confirm MTA-STS rollout plans for inbound email

Estimated remediation effort: 1–2 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 17, 2026

Score

100 75 50 25 0

B-

config.office.com

82/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

5 items need attention

10 passed

Finish setting up email authentication

DMARC / Email Security

2–4 hours High

Spoofed emails can still reach your customers and partners until this is fully enforced. Email authentication for config.office.com is partly set up, but there are gaps: your DMARC policy is "quarantine", so spoofed mail lands in spam instead of being blocked; SPF isn't set up. Until it's fully in place, someone could still send a convincing fake email pretending to be you.

NIST SP 800-177r1§4

Trustworthy Email recommends SPF, DKIM and DMARC for every email domain

How to fix this

1Once your DMARC reports show no legitimate mail failing, change the policy from "quarantine" to "reject" in your domain's DNS settings (check with whoever manages your website or domain registration) so spoofed mail is blocked outright. Your current record with just that change:

v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1

v=spf1 include:_spf.google.com -all

2Add an SPF record in your domain's DNS settings (check with whoever manages your website or domain registration):

3If DKIM signing isn't on yet (we can't confirm it from outside): Turn on DKIM signing — look for "DKIM" under your email provider's admin/security settings. It gives you a record to add in your domain's DNS settings (check with whoever manages your website or domain registration).

4Double-check it's live: search "dmarc record checker" and enter config.office.com.

Email authentication guide

Report unlocked.

View all 10 passed checks

MX Records & Mail Provider

DNS Configuration

DNS CAA Records

TLS Configuration

HSTS Header

TLS Protocol Support

Known Breaches

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 B

811 companies · LynxRadar ranking

Blocking Issues

1/5 present

Missing: X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Fail

Strengths: 1 cookie(s) analyzed. Issues: 1/1 cookie(s) missing Secure flag (OM.SID); 1/1 cookie(s) missing HttpOnly flag (OM.SID); 1/1 cookie(s) missing SameSite attribute (OM.SID).

Likelihood: ★★★★☆

Impact: ★★★★☆

Missing

No SPF record found.

Likelihood: ★★★★★

Impact: ★★★★☆

High Priority

p=quarantine

Strengths: DMARC policy set to quarantine; DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; Forensic reports (ruf) configured. Issues: DMARC policy is 'quarantine', not 'reject' — spoofed mail is moved to spam rather than blocked outright; No SPF record found. Note: DKIM couldn't be confirmed from outside (custom selector names can't be looked up, and some DNS hosts don't expose them), so it isn't counted against the score.

Likelihood: ★★★☆☆

Impact: ★★★☆☆

Medium Priority

Warn

Strengths: MX patterns specified: *.olc.protection.outlook.com; Policy max_age: 7 days. Issues: MTA-STS in testing mode — TLS failures are reported but not enforced; delivery is not protected; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.

Likelihood: ★★☆☆☆

Impact: ★★★☆☆

Best Practice

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: ★☆☆☆☆