← Back to Scanner
F

outlook.com

Posture Score: 47/100

Scanned May 9, 2026 at 1:02 AM UTC

Identity

41

Attack Surface

0

Reputation

99

Identity Findings

FCrDNS failure: no PTR for 52.101.9.18 (outlook-com.olc.protection.outlook.com)
The IP 52.101.9.18 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
high
FCrDNS failure: no PTR for 52.101.68.37 (outlook-com.olc.protection.outlook.com)
The IP 52.101.68.37 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
high
FCrDNS failure: no PTR for 40.93.192.0 (outlook-com.olc.protection.outlook.com)
The IP 40.93.192.0 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
high
FCrDNS failure: no PTR for 52.101.41.7 (outlook-com.olc.protection.outlook.com)
The IP 52.101.41.7 has no PTR record. Forward-confirmed reverse DNS requires a PTR that resolves back to the IP.
💡 Configure a PTR record for the IP that matches the mail server hostname.
high
DMARC policy is monitoring-only (p=none)
The p=none policy only monitors; it does not instruct receivers to quarantine or reject unauthenticated mail.
💡 Upgrade to p=quarantine or p=reject after reviewing aggregate reports.
medium
No PTR record for MX IP: 52.101.9.18
The IP 52.101.9.18 (for outlook-com.olc.protection.outlook.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
medium
No PTR record for MX IP: 52.101.68.37
The IP 52.101.68.37 (for outlook-com.olc.protection.outlook.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
medium
No PTR record for MX IP: 40.93.192.0
The IP 40.93.192.0 (for outlook-com.olc.protection.outlook.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
medium
No PTR record for MX IP: 52.101.41.7
The IP 52.101.41.7 (for outlook-com.olc.protection.outlook.com) has no reverse DNS record.
💡 Configure a PTR record for the mail server IP.
medium
Unknown CAA tag: contactemail
The CAA record contains an unrecognized tag 'contactemail'.
💡 Review the CAA record and use standard tags (issue, issuewild, iodef).
low
Very low TTL on MX record: 195s
The MX record has a TTL of 195s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on A records: 198s
9 A records have a TTL of 198s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on NS records: 285s
4 NS records have a TTL of 285s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on TXT records: 93s
4 TXT records have a TTL of 93s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on SPF record: 93s
The SPF record has a TTL of 93s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
Very low TTL on DMARC record: 285s
The DMARC record has a TTL of 285s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
low
SPF record is valid
The SPF record is properly configured with valid syntax and within lookup limits.
pass
DKIM records are valid
DKIM records found and validated for selectors: selector1, selector2
pass
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
pass
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
pass
ARC support likely available
MX server software appears to support ARC headers for authentication preservation.
pass
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
pass
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
pass
IPv6 readiness is good
IPv6 records are present and properly configured.
pass
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
pass
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
pass
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
pass
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
informational
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
informational
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
informational
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
informational
Deprecated DMARCbis tags found: pct
The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.
informational
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
informational
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
informational
No BIMI record found
BIMI is not configured. Your brand logo will not display in supporting email clients.
informational
Open mail ports on outlook-com.olc.protection.outlook.com
Detected open mail-related ports: 25
informational
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
informational
MX IP network diversity
MX IPs span 2 different /16 networks, providing good diversity.
informational
SOA record parameters
Serial: 2017971531, Refresh: 300s, Retry: 120s, Expire: 2419200s, Min TTL: 60s
informational
Authorized certificate authorities
CAA records restrict certificate issuance to: microsoft.com, digicert.com, globalsign.com, entrust.net
informational

Attack Surface Findings

Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.23
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.23, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.15
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.15, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.10
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.10, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.12
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.12, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.22
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.22, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.24
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.24, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.19
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.19, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.26
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.26, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.16
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.16, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.28
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.28, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.18
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.18, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.27
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.27, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.14
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.14, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.13
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.13, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.11
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.11, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Non-routable IPv4 in public DNS: test.outlook.com → 10.10.10.17
The subdomain test.outlook.com resolves to non-routable IP 10.10.10.17, leaking internal network information.
💡 Remove non-routable IPs from public DNS or implement split-horizon DNS.
high
Domain enumerability: medium
The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
medium
DNSSEC is not enabled
No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.
💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.
medium
No excessive DNS information exposure detected
No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.
pass
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
pass
8 subdomain(s) discovered for outlook.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
informational
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for outlook.com and its subdomains. Each certificate reveals subdomain names.
informational

Reputation Findings

HSTS enabled but missing preload directive on outlook.com
Strict-Transport-Security: max-age=31536000; includeSubDomains
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
low
security.txt present
Found security.txt at https://outlook.com/.well-known/security.txt.
pass
TLS certificate valid for 146 days
Certificate for outlook.com expires on 2026-10-02.
pass
Certificate issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1
The certificate for outlook.com is issued by a third-party CA.
pass
Signature algorithm: rsa-sha256
The certificate for outlook.com uses an acceptable signature algorithm.
pass
RSA key: 2048 bits
The certificate for outlook.com uses an adequate RSA key of 2048 bits.
pass
SCTs present in certificate
The certificate for outlook.com contains Signed Certificate Timestamps.
pass
No weak ciphers detected
No known weak cipher suites detected on outlook.com.
pass
Domain valid for 100 days
Domain outlook.com expires on 2026-08-17.
pass
Domain transfer and delete locks enabled
Domain outlook.com has clientTransferProhibited and clientDeleteProhibited locks.
pass
TLD has good reputation
The .com TLD is not on known abuse watchlists.
pass
DMARC reporting destinations look legitimate
DMARC rua/ruf addresses do not point to known URL shortener services.
pass
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
pass
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
informational
Abuse contact lookup failed
Could not query abuse contact information.
informational
PhishTank — API key required
PhishTank phishing database check requires an API key.
informational
Sender Score — API key required
Sender Score reputation check requires an API key.
informational
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
informational
Could not connect to webmail.outlook.com
HTTPS request to https://webmail.outlook.com failed or timed out.
informational
WHOIS registration data
Registrar: MarkMonitor Inc. | Created: 1994-08-18 | Expires: 2026-08-17 | Updated: 2025-07-16
informational
WHOIS privacy protection not detected
Domain outlook.com does not appear to have WHOIS privacy protection. Registrant details may be publicly visible.
informational

Dependency Chains

DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record SPF record found and configured → DMARC Policy DMARC policy: none
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature DKIM signature missing → DMARC Policy DMARC policy: none
⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.
Mail Server Identity: outlook-com.olc.protection.outlook.com
PTR record proves mail server legitimacy
MX: outlook-com.olc.protection.outlook.com Mail server at 52.101.9.18 → PTR Record No PTR record
⚠️ Mail server outlook-com.olc.protection.outlook.com (52.101.9.18) lacks a PTR record. Many receiving servers require matching forward and reverse DNS for spam prevention.
Mail Server Reputation: outlook-com.olc.protection.outlook.com
RBL check ensures server is not blacklisted
MX: outlook-com.olc.protection.outlook.com Mail server at 52.101.9.18 → RBL Status Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support Mail servers support TLS encryption → MTA-STS Policy Mode: enforce
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement DMARC not enforced (p=none or missing) → BIMI Record BIMI not configured
⚠️ DMARC is not enforced. BIMI requires a DMARC policy of "quarantine" or "reject" to prove you have strong email authentication. Without enforcement, email clients will not display your logo.
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support Mail servers support TLS encryption → TLS-RPT Reporting TLS failure reporting configured

Security Checks

MX Records
✓
SPF Record
✓
DKIM Record
✗
DMARC Policy
✓
BIMI Record
✗
CAA Records
✓
DNSSEC
✗
MTA-STS
✓
TLS-RPT
✓

Embed Badge

Display your domain's security grade on your website or README:

outlook.com Email Security Grade
<img src="https://scan.ractermx.com/badge/outlook.com.svg" alt="Email Security Grade">

Want to re-scan this domain for updated results?

Scan outlook.com Again