DNS Gurus
Cached · just now
91/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 8
Google Trust logo Google Trust Google API JS Client logo Google API JS Client Google Static File Front End logo Google Static File Front End LaunchDarkly logo LaunchDarkly PostHog logo PostHog Sentry logo Sentry Stripe logo Stripe Google Cloud logo Google Cloud

Certificate Information

Subject
CN=app.notablehealth.com
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
March 22, 2026
Valid Until
June 20, 2026 89 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C8:1B:70:86:60:77:C1:BD:09:90:E1:2C:77:83:2B:66:C0:D3:18:62:9D:D6:5C:A7:35:05:97:0D:CD:AA:F9:DA
Alternative Names
1 domains

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=31104000; includeSubDomains
Content-Security-Policy
LaunchDarkly logo
Basic
default-src; worker-src; base-uri; +12 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
no-referrer
Permissions-Policy
Present
geolocation=(self)
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • 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

Subject Alternative Names

1 domain
app.notablehealth.com