Responsible Disclosure | Static Frontend Security | Bypass Strictly Prohibited
Found a security issue or exploit? Please help keep this project safe for everyone!
- Do NOT open a public issue for vulnerabilities.
- Email your findings directly to:
- If possible, include:
- Steps to reproduce
- Screenshots or code snippets
- Impact assessment (if known)
- We will respond as quickly as possible and coordinate a fix or mitigation.
- Get credit on the repoβs acknowledgements (if desired)!
This project is fully static (HTML, CSS, JS on GitHub Pages).
There is no backend, no database, and no server-side logic. All verification and session management are handled in the browser.
- Session tokens:
Stored inlocalStorage, valid for up to 6 hours. - No sensitive secrets:
All logic is public and open source by design. - Redirects:
Implemented indd.htmlusing session checks and fallback timers. - Browser support:
Latest versions of Chrome, Firefox, and Edge are recommended for best security.
- Frontend-only:
Do not use this for high-risk authentication or sensitive data protection. - No passwords or personal data should ever be collected.
- Session tokens are not cryptographically secure; they're for basic verification only.
- For stronger security (e.g., for sensitive forms), pair this with a backend or use a service with proven bot protection.
- Keep dependencies up-to-date to avoid known vulnerabilities.
- Use HTTPS to serve your site for secure transport (GitHub Pages does this automatically).
- Bypass strictly prohibited:
Any method, tool, or advice to bypass the verification, token, or redirect mechanism is strictly prohibited and not tolerated.
If you discover a bypass, report it privatelyβdo not share, demonstrate, or use it.
- This project includes a Support & Verify system designed for modular, client-side human verification.
- Always use the latest version available for the best security practices and features.
- Visit: support.deepdeyiitk.com for documentation and updates.
- Make sure your browser allows localStorage (not in private/incognito mode).
- Some extensions may block storage APIs; try in a clean browser profile.
- Confirm youβre accessing via HTTPS and not file://
- Check the redirect URL in
dd.htmlis set correctly:
// dd.html
const REDIRECT_TARGET = "https://docs.google.com/forms/d/e/1FAIpQLSdqcVijtxP2qtiwFtuS-NFBL9_Pnbf6WwiydLnzh4nbxQWy1Q/viewform";
if (localStorage.getItem("verifiedToken")) {
window.location.href = REDIRECT_TARGET;
} else {
setTimeout(() => {
window.location.href = "index.html";
}, 7000);
}- Check for JavaScript errors in the browser console.
- Ensure all scripts are loaded properly and not blocked by browser settings.
- Complete verification modules as intended.
- Attempting, facilitating, or publishing bypass or circumvention techniques is STRICTLY PROHIBITED.
- Access the redirect page (
dd.html) without a valid token only to report flaws, never for malicious purposes. - Test on multiple browsers and devices.
- Report any unintended access or unexpected behavior!
We appreciate responsible security research.
Please give us a chance to address issues before public disclosure.
- Private reports = faster, safer fixes for all users.
- Credit will be given in the repo (if desired).
- For urgent issues, mention βSECURITYβ in your email subject.
| Version | Supported |
|---|---|
| Latest | β Support & Verify [UPDATED] {Latest} |
- Regular dependency checks (for any external libraries or npm packages)
- Review all code contributions for security risks before merging
- Community feedback is always welcome!
Your contributions make this project safer and better for everyone.
Designed & Maintained with β€οΈ by Deep Dey β Modular, Frontend-Only, Security-Conscious
