Open
Cached
·
just now
90/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
HubSpot Forms
Intercom
LinkedIn
Sanity
Segment
Sentry
Typeform
Vimeo
Wistia
Google Cloud
Certificate Information
Subject
CN=links.urllo.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
May 02, 2026
Valid Until
July 31, 2026
84 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
88:A0:B2:5C:2D:68:14:A5:30:DA:BF:92:B5:28:2B:43:C9:14:44:78:68:26:F8:0B:C9:6C:66:98:76:D9:00:CE
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
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