Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
Adobe Target
Adobe Audience Manager
Adobe Dynamic Tag Management
Adobe Marketo
Akamai
Active incidents
AppNexus (Xandr)
Active incidents
AWS
Azure Blob Storage
AzureFrontDoor
Azure Monitor
Microsoft Advertising
DigiCert
Facebook
GeoTrust
Google DoubleClick
Google Search
Google Static File Front End
HubSpot
HubSpot Forms
LinkedIn
Microsoft Clarity
Microsoft 365
Google Cloud
Microsoft Azure
Certificate Information
Subject
CN=dev-about.ads.microsoft.com
Issuer
C=US, O=DigiCert Inc, OU=www.digicert.com, CN=GeoTrust TLS RSA CA G1
Valid From
May 17, 2026
Valid Until
November 17, 2026
84 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
47:01:F2:DE:19:F1:91:A7:E8:E5:A4:3E:A1:85:11:F3:BE:EA:C6:B4:DD:EF:0F:66:42:3B:5E:DC:8D:48:5C:66
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
Excellent
max-age=31536000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • 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