Open
Cached
·
just now
92/100
SECURITY SCORE
Detected Technologies
Let's Encrypt
Ahrefs
Bing
Microsoft Advertising
Cookiebot
Cookie Information
Demandbase
Facebook
Google AdSense
Google Analytics
Google DoubleClick
Google Search
Google Tag Manager
hCaptcha
HubSpot
Active incidents
HubSpot Analytics
Active incidents
HubSpot Forms
Active incidents
HubSpot Live Chat
Active incidents
LinkedIn
Matomo
Pusher
Sentry
Statuspage
YouTube
Zendesk
Certificate Information
Subject
CN=gatewayapi.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
April 07, 2026
Valid Until
July 06, 2026
65 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
68:24:6C:82:6E:12:B1:1A:28:D4:0A:C7:E6:DC:72:46:45:3B:65:81:92:BF:A1:40:7F:97:30:A1:84:88:9C:3C
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