Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Google Trust
UserWay
AzureFrontDoor
BootstrapCDN
Ceros
Cloudflare CDNJS
Crazy Egg
Demandbase
Elfsight
Google AdSense
Google Analytics
Google Conversion Tracking
Google DoubleClick
Google Fonts
Google Search
Google Static File Front End
Google Tag Manager
Issuu
jsDelivr
LinkedIn
MyFonts
NitroPack
Salesforce Pardot
SalesLoft
Securiti
Twitter
Vimeo
YouTube
Google Cloud
Microsoft Azure
Certificate Information
Subject
CN=forte.net
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 17, 2026
Valid Until
July 16, 2026
78 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
E7:AF:F3:9E:21:B0:79:9A:50:CB:74:EE:69:16:9F:2F:06:C5:0C:62:8A:78:F7:70:FA:81:CF:C1:B3:C8:9D:19
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
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
accelerometer=(), autoplay=(), camera=(); +11 more
Recommendations
- • Consider adding 'preload' to HSTS for maximum security
- • 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