Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS API Gateway
AWS CloudFront
Google Trust
Gravatar
AppNexus (Xandr)
AppsFlyer
AWS
Active incidents
Amazon S3
Bing
Facebook
Google Analytics
Google Cloud Functions
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Optimize
Google Search
Google Static File Front End
Google Tag Manager
Intercom
jsDelivr
LaunchDarkly
New Relic
Pantheon
Twitter
YouTube
Google Cloud
Certificate Information
Subject
CN=m1.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 17, 2026
Valid Until
July 16, 2026
52 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
D8:6A:8F:6C:39:94:04:04:4B:97:FC:0B:A6:A0:01:7A:9C:60:74:88:C5:EC:01:33:78:82:0E:FF:5A:C3:0A:35
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=31536001; includeSubDomains; preload, max-age=300
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