DNS Gurus
Cached · just now
92/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 7
Google Trust logo Google Trust Google Analytics logo Google Analytics Google API JS Client logo Google API JS Client Google Cloud Functions logo Google Cloud Functions Google Cloud Run logo Google Cloud Run Google Fonts logo Google Fonts Google Tag Manager logo Google Tag Manager

Certificate Information

Subject
CN=muvcredit.com.br
Issuer
C=US, O=Google Trust Services, CN=WR3
Valid From
March 01, 2026
Valid Until
May 31, 2026 51 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
39:9E:CE:82:04:E6:1A:74:34:A4:C3:33:3E:A1:43:94:D6:FC:1A:18:CC:8D:E3:FF:6D:FB:B6:DD:0D:19:98:E7
Alternative Names
3 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=31556926
Content-Security-Policy
Google Analytics logo
Good
default-src; script-src; style-src; +6 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
strict-origin-when-cross-origin
Permissions-Policy
Present
geolocation=(), microphone=(), camera=()
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Strengthen CSP by removing 'unsafe-eval'

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