Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Ahrefs
Bing
Microsoft Advertising
Cookiebot
Cookie Information
Demandbase
DigiCert
Facebook
Google AdSense
Google Analytics
Google DoubleClick
Google Search
Google Tag Manager
hCaptcha
HubSpot
HubSpot Analytics
HubSpot Forms
HubSpot Live Chat
LinkedIn
Matomo
Pusher
RapidSSL
Sentry
Statuspage
YouTube
Zendesk
Certificate Information
Subject
CN=*.gatewayapi.com
Issuer
C=US, O=DigiCert Inc, OU=www.digicert.com, CN=RapidSSL TLS RSA CA G1
Valid From
May 19, 2025
Valid Until
June 13, 2026
45 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
3C:42:51:6E:A8:4F:AA:1A:0F:87:C6:01:7E:90:75:1B:12:F9:82:60:6B:5D:17:B1:B5:C7:3B:03:6A:66:0E:A9
Alternative Names
Security Configuration
TLS Protocols
TLS 1.0
TLS 1.1
TLS 1.2
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
Warnings
- • TLS 1.1 is deprecated and should be disabled
- • TLS 1.0 is deprecated and should be disabled
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=31536000
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
camera=(), display-capture=(), fullscreen=(); +2 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Strengthen CSP by removing 'unsafe-eval'
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