SSL Verification Bypassed
The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.
Reason:
Hostname Mismatch - certificate is issued for reroute443.microsoft.com, not for blog.bingads.com
Open
Cached
·
just now
86/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=reroute443.microsoft.com
Issuer
C=US, O=Microsoft Corporation, CN=Microsoft Azure RSA TLS Issuing CA 08
Valid From
December 14, 2025
Valid Until
June 12, 2026
145 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
11:40:CF:F4:FC:50:2B:C9:04:E1:3B:EA:D4:E9:5D:70:52:3E:57:3F:46:71:C5:6B:BA:5A:03:D0:6C:0F:DA:65
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=63072000; includeSubdomains; preload
Content-Security-Policy
Basic
default-src; script-src; style-src; +5 more
default-src 'self' www.microsoft.com; script-src 'self' www.microsoft.com js.monitor.azure.com assets.adobedtm.com wcpstatic.microsoft.com mem.gfx.ms 'unsafe-inline' 'unsafe-eval' snap.licdn.com *.clarity.ms *.google.com www.gstatic.com 204-kzg-685.mktoweb.com bat.bing.com acdn.adnxs.com msamarketing.z22.web.core.windows.net admin.microsoft.com adsuxsiwest.blob.core.windows.net adsuxprodfd-awb5gsddabddbqgv.z01.azurefd.net adsuxsiwestfd-ahfeakeyhtafghd0.z01.azurefd.net *.api.sandbox.ads.microsoft.com *.api.ads.microsoft.com directline.botframework.com petrol-int.office.microsoft.com petrol.office.microsoft.com *.omnichannelengagementhub.com browser.pipe.aria.microsoft.com us-prod.asyncgw.teams.microsoft.com edge.skype.com customervoice.microsoft.com adrecommendation.api.sandbox.ads.microsoft.com adrecommendation.api.ads.microsoft.com res.cdn.office.net; style-src 'self' www.microsoft.com 'unsafe-inline' 204-kzg-685.mktoweb.com; font-src 'self' c.s-microsoft.com www.microsoft.com res-1.cdn.office.net data:; img-src 'self' data: img-prod-cms-rt-microsoft-com.akamaized.net googleads.g.doubleclick.net www.facebook.com px.ads.linkedin.com *.google.com *.google.co * dev-about.ads.microsoft.com qa-about.ads.microsoft.com about.ads.microsoft.com blob:; connect-src 'self' wss: 'unsafe-inline' *.google.com js.monitor.azure.com assets.adobedtm.com wcpstatic.microsoft.com mem.gfx.ms px.ads.linkedin.com mscom.demdex.net browser.events.data.microsoft.com d.clarity.ms target.microsoft.com dpm.demdex.net *.clarity.ms/collect bat.bing.com dev-about.ads.microsoft.com qa-about.ads.microsoft.com about-uat.ads.microsoft.com beta-about.ads.microsoft.com about.ads.microsoft.com *.adnxs.com consentreceiverfd-prod.azurefd.net adsuxprodfd-awb5gsddabddbqgv.z01.azurefd.net adsuxsiwestfd-ahfeakeyhtafghd0.z01.azurefd.net msftenterprise.sc.omtrdc.net westus2-2.in.applicationinsights.azure.com bat.bing.net msamarketing.z22.web.core.windows.net *.microsoft.com adsuxsiwest.blob.core.windows.net *.api.sandbox.ads.microsoft.com *.api.ads.microsoft.com directline.botframework.com petrol-int.office.microsoft.com petrol.office.microsoft.com *.omnichannelengagementhub.com browser.pipe.aria.microsoft.com us-prod.asyncgw.teams.microsoft.com edge.skype.com comms.omnichannelengagementhub.com *.trouter.skype.com *.communication.azure.com us-prod.asyncgw.teams.microsoft.com adrecommendation.api.sandbox.ads.microsoft.com adrecommendation.api.ads.microsoft.com res.cdn.office.net; frame-src 'self' *.google.com * 204-kzg-685.mktoweb.com www.microsoft.com; media-src 'self' blob: dev-about.ads.microsoft.com qa-about.ads.microsoft.com about-uat.ads.microsoft.com beta-about.ads.microsoft.com about.ads.microsoft.com;
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Not Configured
(Any CA can issue certificates)
CAA Issues
- • No CAA records configured - any CA can issue certificates
Recommendations
- • Implement CAA records to restrict which CAs can issue certificates for your domain
- • This adds an extra layer of security against unauthorized certificate issuance
- • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
- • Consider adding 'iodef' record to receive security incident reports