Host · tessellatepay.com · Production · criticality A
200 · Sign in · Tessellate Pay · Cloudflare edge · 3 open issues · first seen 2 Sep · last scanned Mon 12 Oct · scanning now, since 10:19
Origin leak · 18.133.42.7 · found in certificate logs
Cloudflare protects app.tessellatepay.com, but its server's own address is in public certificate logs. Requests sent straight to it skip the firewall and rate limits.
What to fix on it first
3 issues · ranked by proof, then exploitation in the wild, then severity
Gone since Mon 5 Oct · 1 fixed
Who gets its findings, and how much it matters
Owner routes findings · criticality moves them up the queue
What it's for
What customers use
Criticality
Money moves or customer data lives here
What answers, from where, running what
As the last finished scan saw it
On the web
How it meets the internet
Behind your edge
Cloudflare or CloudFront answers first: a firewall and rate limits in front.
But its origin leaks, so the edge can be walked around.
Runs
What it offers anyone who asks
Open ports, the headers its pages send, the routes we know
Ports
Not scanned: it's behind a CDN, so the edge would answer, not this server.
Headers
1,401 routes known: 1,186 pages, 212 API routes, 3 forms
Explore them