Open
Cached
·
just now
92/100
SECURITY SCORE
Certificate Information
Subject
C=US, ST=Texas, L=Austin, O=HID GLOBAL CORPORATION, CN=docs.hidglobal.com
Issuer
C=US, O=IdenTrust, OU=TrustID Server, CN=TrustID Server CA O1
Valid From
November 11, 2025
Valid Until
November 11, 2026
286 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
7A:84:D2:54:E9:A0:3F:15:A3:47:9C:5F:84:7E:D2:4B:A0:4B:18:F5:62:B0:9E:AF:1B:96:24:48:48:11:3E:8E
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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Basic
frame-ancestors; object-src; script-src; +2 more
frame-ancestors 'self' https://www.hidglobal.com/; object-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cse.google.com/cse.js https://ajax.googleapis.com/ajax/libs/jquery/3.5.1/jquery.min.js https://www.googletagmanager.com/gtm.js https://cdnjs.cloudflare.com/ajax/libs/highlight.js/11.7.0/highlight.min.js https://maxcdn.bootstrapcdn.com/bootstrap/3.4.1/js/bootstrap.min.js https://cdnjs.cloudflare.com/ajax/libs/html2pdf.js/0.9.3/html2pdf.bundle.min.js https://cdn.jsdelivr.net/jquery.validation/1.16.0/jquery.validate.min.js https://www.google.com/cse/static/element/ https://cse.google.com/adsense/search/ https://cse.google.com/cse/element/ https://www.gstatic.com/prose/ ; img-src 'self' https://clients1.google.com/generate_204 https://www.google.com/cse/static/images/1x/en/branding.png https://www.google.com/cse/static/images/2x/en/branding.png; connect-src 'self' https://api.madcapcentral.com/ https://hidglobal3.api.madcapcentral.com/
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer-when-downgrade
Permissions-Policy
Present
geolocation=(self), camera=(self), microphone=(self)
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