SSO and MFA Login Surface Analyzer
Enter a login URL or hostname to see which SSO providers, MFA signals and form protections are visible without signing in.
What it checks
- Detects SSO providers from redirects, page content and script hosts: Azure AD, Okta, Auth0, Google, GitHub, Keycloak, ADFS, Ping Identity, OneLogin, Duo and AWS Cognito
- Checks the openid-configuration path and four common SSO paths
- Looks for MFA signals: WebAuthn or passkeys, TOTP, SMS or email OTP, push, hardware tokens and backup codes
- Reviews the login form for a CSRF field, POST method, CAPTCHA and password policy hints, and lists cookie flags and security headers
How to read the result
- Signals from third-party script hosts are matched as text and not fetched. Scripts are fetched only when they are on the same origin, up to six of them.
- Missing MFA signals mean the tool did not see them on the visible pages. MFA is often presented after the password step, so it may still exist.
- The result is a snapshot of what is visible before sign-in. It does not show how the provider enforces MFA or session policy.
What it does not tell you
The tool never signs in, submits forms or tries credentials, and it does not measure how strong authentication is. It sees only pages reachable without signing in. This is not a penetration test.
Data sources
GET and HEAD requests to the login page origin, the openid-configuration path, four generic SSO paths and up to six same-origin scripts, all with timeouts and checked for public addresses.
No login · 10 calls / minute / IP · Data stored in the EU
FAQ
Does the tool try to log in?
No. It sends only GET and HEAD requests and never submits a form or sends credentials.
Why are my MFA signals not found?
The tool reads only what is visible without signing in, and only up to six same-origin scripts. MFA prompts that appear after the password step are not seen.
What is the rate limit?
Ten calls per minute per IP address for anonymous use.
Go deeper: Web Pentest engine (OWASP Top 10 coverage)