Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
YouTube
Algolia
Amazon S3
Customer.io
Datadog
Facebook
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google reCAPTCHA
Google Search
Google Static File Front End
Google Tag Manager
HubSpot
Active incidents
HubSpot Forms
Active incidents
Intercom
LinkedIn
Sanity
Segment
Sentry
Typeform
Vimeo
Wistia
Google Cloud
Certificate Information
Subject
CN=urllo.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
March 16, 2026
Valid Until
June 14, 2026
43 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
D8:25:C8:47:CB:40:11:97:04:DF:D8:65:75:AB:A6:8D:06:55:5C:29:AD:3E:54:10:62:F0:AB:DD:0B:46:53:2B
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=63072000; includeSubDomains; preload
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Strengthen CSP by removing 'unsafe-eval'
- • 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
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
- • Consider adding 'issuewild' records to control wildcard certificate issuance