Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Let's Encrypt
YouTube
Google Tag Manager
Bugsnag
Bing
G2
Sanity
Reddit
Cookiebot
Google DoubleClick
Google Analytics
ClickCease
Microsoft Advertising
Google Conversion Tracking
Pusher
BugHerd
Google Static File Front End
Google Fonts
Wistia
Algolia
Hotjar
LinkedIn
ZoomInfo
Adobe Marketo
Qualified
Storylane
Facebook
Amazon S3
StackAdapt
Simplecast
jQuery
MNTN
Vimeo
Lever
Sentry
jsDelivr
Google Cloud
Certificate Information
Subject
CN=firstup.io
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
March 18, 2026
Valid Until
June 16, 2026
48 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
07:CE:3C:BC:55:F9:98:F2:B2:AD:59:CE:D5:61:DC:16:54:30:FD:40:F1:F1:25:B6:C0:EC:77:B9:8C:A3:9C:F7
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
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), microphone=*, geolocation=()
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
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