Open
Cached
·
just now
91/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Algolia
Amazon S3
Cloudflare CDNJS
Contentful
Esri
Facebook
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Optimize
Google Search
Google Tag Manager
HubSpot
HubSpot Analytics
HubSpot CMS
HubSpot Feedback & Surveys
HubSpot Forms
HubSpot Live Chat
HubSpot Video
LinkedIn
Microsoft Clarity
Sketchfab
Twitter
Vimeo
YouTube
Certificate Information
Subject
CN=pix4d.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 19, 2026
Valid Until
July 18, 2026
72 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D7:98:56:3E:A8:22:6A:A0:D6:C3:E9:01:D4:7B:97:0A:E8:E6:A2:11:FD:97:13:0A:A4:1B:85:47:AC:88:E1:61
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
Good
max-age=31536000; includeSubDomains
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Missing
Not configured
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
- • Consider adding Permissions-Policy to control browser features
CAA Records (Certificate Authority Authorization)
CAA Records
Configured
(Restricts certificate issuance)
Current Issuer
Authorized
(Matches CAA policy)
Authorized CAs
Incident Reporting
mailto:[email protected]
Recommendations
- • Consider using critical flag (flags=128) for stricter CAA enforcement
- • You have authorized 5 CAs - consider limiting to only the CAs you actively use
- • Consider adding 'issuewild' records to control wildcard certificate issuance