Open
Cached
·
just now
95/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Google Maps
Google Tag Manager
Bing
G2
PathFactory
Reddit
Tapad
Liveramp
HubSpot Forms
Cookiebot
OptinMonster
DigiCert
Google DoubleClick
AdRoll
Google Analytics
Microsoft Advertising
Crazy Egg
Google Conversion Tracking
Google Static File Front End
Google Fonts
Bizzabo
LinkedIn
ZoomInfo
HubSpot Analytics
unpkg
Google Search
Demandbase
Qualified
Facebook
Amazon S3
StackAdapt
Salesforce Pardot
IP-API
HubSpot
YouTube
The Trade Desk
Microsoft Clarity
jsDelivr
Google Cloud
Certificate Information
Subject
C=US, ST=New Jersey, L=Clark, O=NB Ventures Inc, CN=*.gep.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
August 18, 2025
Valid Until
September 18, 2026
32 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
B8:82:C3:37:2F:BE:7C:7C:89:49:FC:0D:5B:9D:96:1A:43:CA:FF:A4:5F:EB:E5:48:2F:2E:73:F1:42:1B:4D:31
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
Good
strict-origin
Permissions-Policy
Present
interest-cohort=()
Recommendations
- • 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