Troubleshooting & glossary
If something goes wrong
| What you see | What to try |
|---|---|
| Redirected to login repeatedly | Session expired—sign in again. |
| Onboarding won’t finish | Finish domain verification; if a step stays blocked, ask internal IT or security using your normal process. |
| Typosquatting empty or old | Wait for a scan; confirm primary domain in Settings; if it persists, report it through internal support. |
| 403 / permission message | Use your organization’s usual channel for access or application issues. |
| 500 or generic error | Try again later; if it keeps happening, report it through internal support so the deployment can be checked. |
Infrastructure issues (servers, databases, networking) are resolved outside the help pages you are reading now.
Quick glossary
| Term | Meaning |
|---|---|
| Workspace | Shared PhishEye data for your organization (brand, domain, scan results). |
| Primary domain | The domain typosquatting is anchored to. |
| Typosquat / permutation | A look-alike domain generated for checks. |
| Free-host row | A candidate on a known free host pattern (e.g. something.pages.dev). |
| Finding | A tracked issue in Findings. |
| Takedown case | Abuse-report workflow with a timeline. |
Detailed deployment documentation ships with the application repository.