Open
Cached
·
just now
89/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
YouTube
Google AdSense
Dreamdata
HubSpot Video
Google Tag Manager
Bing
SalesLoft
Sectigo
GrowthBook
Reddit
HubSpot Forms
Capterra
HubSpot Feedback & Surveys
Google DoubleClick
Google Analytics
Microsoft Advertising
Typeform
Google Static File Front End
Google Fonts
Wistia
Twitter
Hotjar
LinkedIn
HubSpot CMS
HubSpot Analytics
Google Search
Facebook
Amazon S3
HubSpot
Intercom
Quora
Microsoft Clarity
HubSpot Live Chat
Google Cloud
Certificate Information
Subject
CN=*.nordlayer.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA DV R36
Valid From
September 15, 2025
Valid Until
October 16, 2026
170 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
66:6B:A9:79:06:FA:2C:93:4D:E9:F6:65:69:5E:99:9F:38:6C:73:EC:CC:83:71:58:E6:8E:54:FA:93:92:9F:C0
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
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • 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