Open
Cached
·
just now
88/100
SECURITY SCORE
Detected Technologies
AWS CloudFront
Atlassian Jira
AWS
Active incidents
Amazon S3
Box
Cloudflare Stream
DigiCert
Font Awesome
Google Analytics
Google API JS Client
Google Fonts
Google Hosted Libraries
Google Search
Google Static File Front End
Google Tag Manager
Google Translate
Heap
HubSpot Forms
Mixpanel
Sentry
Microsoft SharePoint
Unsplash
Vimeo
Weglot
YouTube
Google Cloud
Certificate Information
Subject
C=NL, L=Amsterdam, O=BearingPoint IP Holding B.V., CN=hi.bearingpoint.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
December 09, 2025
Valid Until
January 06, 2027
166 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
67:CC:26:BE:CB:F6:A8:52:B6:09:E3:9B:7E:38:5F:BB:88:79:CB:B1:4F:84:A5:8B:79:1D:42:63:4E:9A:1C:BF
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
Present
max-age=31536000; IncludeSubDomains;
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
accelerometer=(), ambient-light-sensor=(), autoplay=(); +38 more
Recommendations
- • Increase HSTS max-age to at least 1 year and add includeSubDomains
- • Improve CSP by adding more specific directives and removing 'unsafe-inline'
- • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
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