hogum
expo.io

expo.io security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

5risk

Low

Minor observations only.

0Critical
0High
0Medium
2Low
1Info
Collected 16.1sfrom cache
  1. Certificate Transparency
  2. DNS resolution2
  3. Network ownership0
  4. CDN / WAF detection0
  5. Exposed ports & CVEs26
  6. Registration
  7. DNS posture2
  8. Email authentication2
  9. Certificate
  10. Security headers4
  11. Archived URLs
  12. Analysis3
  • noteCertificate Transparency did not complete (HTTP 502). Results below are partial.
  • noteCertificate inspection is unavailable in this runtime.
  • noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
  • noteCDN/WAF detection is unavailable in this runtime.
  • noteNo registration data: RDAP has no record at this level.
  • note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.
final https://expo.dev/status 200time 294msstack cloudflare
  • http:// redirects to https://
  • Strict-Transport-Security
    max-age=31536000; includeSubDomains
  • Content-Security-Policy
    default-src 'self' https://static.expo.dev; connect-src 'self' https://api.expo.dev wss://logs.expo.dev https://static.expo.dev https://job-artifacts.eascdn.net…
  • Clickjacking protection
    SAMEORIGIN
  • X-Content-Type-Options
    nosniff
  • Referrer-Policy
  • Permissions-Policyoptional
  • security.txt published
AddressPortsCVEsEdgeNetwork
172.67.149.36
80443205220532082208320862087+5
0Cloudflare~
104.21.55.146
80443205220532082208320862087+5
0Cloudflare~
Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.