Cached · just now
89/100 SECURITY SCORE

Certificate Information

Subject
CN=luno.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 16, 2026
Valid Until
July 15, 2026 74 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
E5:BC:51:57:31:62:BE:84:66:B0:9B:75:DE:95:CE:B2:3B:20:ED:F5:68:32:2F:F1:71:74:80:34:EB:DF:A3:0F
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=60
Content-Security-Policy
Good
default-src; script-src; style-src; +10 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
camera=(self "https://emea-face-quality.identityx-cloud.com" "https://sdk.onfido.com"), microphone=(self "https://emea-face-quality.identityx-cloud.com" "https://sdk.onfido.com"), geolocation=(self "https://*.geocomply.net" "https://geocomply.net" "https://sdk.onfido.com"); +26 more
Recommendations
  • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • Strengthen CSP by removing 'unsafe-eval'
  • 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

Subject Alternative Names

2 domains