Open
Cached
·
just now
93/100
SECURITY SCORE
Detected Technologies
Gravatar
AWS CloudFront
Let's Encrypt
YouTube
Google Tag Manager
Bing
Esri
AppNexus (Xandr)
Yahoo
Google DoubleClick
Google Analytics
Google Conversion Tracking
Libsyn
New Relic
Cloudflare CDN
Basis Technologies
Google Static File Front End
Google API JS Client
Twitter
Issuu
LinkedIn
Zendesk
Mapbox
Google Search
BootstrapCDN
Cloudflare
Facebook
Eventbrite
Amazon S3
Lucky Orange
Adobe Fonts (Typekit)
Vimeo
Elfsight
Highcharts
The Trade Desk
Microsoft Clarity
Font Awesome
MyFonts
jsDelivr
Google Cloud
Certificate Information
Subject
CN=smeco.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 16, 2026
Valid Until
July 15, 2026
80 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
FA:53:B4:C8:6A:FF:73:D4:47:85:D7:91:3A:A2:79:2A:E5:75:0D:DC:3A:09:35:B0:E0:D9:25:1F:7B:32:61:08
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
Present
same-origin
Permissions-Policy
Present
accelerometer=(), autoplay=(), cross-origin-isolated=(); +16 more
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