Open
Cached
·
just now
90/100
SECURITY SCORE
Detected Technologies
Google Trust
AWS CloudFront
Google Tag Manager
Uberflip
G2
FunnelFuel
SalesLoft
Google Hosted Libraries
Reddit
Liveramp
Google DoubleClick
Google Analytics
Crazy Egg
Yoast
Google Static File Front End
Metadata.io
Google Fonts
Wistia
Sprinklr
Active incidents
LinkedIn
Google Search
BootstrapCDN
Adobe Marketo
Demandbase
Kaltura
Facebook
OneTrust
Adobe Fonts (Typekit)
Cloudflare CDNJS
Google Optimize
Akamai
Active incidents
YouTube
Font Awesome
MyFonts
jsDelivr
Google Cloud
Certificate Information
Subject
CN=info.pros.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 09, 2026
Valid Until
June 07, 2026
35 days
Public Key
ECDSA
256 bit
(P-256)
Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
15:A0:77:5F:42:28:81:6D:E3:10:0E:5A:D1:CF:A2:1F:1E:26:08:E4:7A:A8:ED:D7:32:45:38:B8:1F:EF:6F:D3
Alternative Names
Security Configuration
TLS Protocols
TLS 1.2
Forward Secrecy
Limited
(Check cipher configuration)
Warnings
- • TLS 1.3 is not supported (recommended)
HTTP Security Headers
Status
Strict-Transport-Security
Good
max-age=63072000; includeSubDomains
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), autoplay=(), camera=(); +19 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