Contact ByteBreach Command
Last Updated: October 2026
ByteBreach Security Academy is run by a small team of network and security engineers who publish the curriculum, maintain the lab environment, and answer learner questions. Whether you are stuck on a CCNA lab, reporting a broken challenge, proposing a new track, or asking about sponsorship and partnerships, this is the page that gets you to a human. Every message is read by a real maintainer, and we publish the channels we actually monitor so you can choose the fastest route.
How to reach us
Use the secure inbound form below for anything that needs a written record, including account issues, takedown requests, intellectual property enquiries, and formal notices. The form writes directly into our internal support queue and triggers an instant alert to the on-call maintainer, so nothing sits unread. For a quick question, a bug in one specific lab, or a tip, the community channels are usually faster because they are monitored continuously.
The email address below is the official contact point for this domain. It is also the address that Google AdSense, Google AdMob, and the Amazon Appstore use for policy verification, so it is monitored continuously rather than once a week.
Transmit an inquiry
Every field below helps us answer on the first attempt. Please include the name of the track or lab, the room or challenge identifier, and the exact point where you got stuck. If a task produced an error, copy the terminal output or the browser console message exactly as it appeared rather than paraphrasing it, because the wording is usually what identifies the cause.
What to include in your message
- Track and module. For example, “CCNA → OSPF neighbour troubleshooting, room 3”. This is the fastest way for us to reproduce your state.
- What you expected and what happened. The expected output and the actual error or incorrect result, copied verbatim.
- Device and browser context. Whether you are in the web app, the Android app, or a lab console, plus your operating system and browser version when the problem is a rendering or layout issue.
- Your account identifier. The email address you sign in with, so we can look up your progress and unlock state. Please do not send us a password.
- A clear ask. Whether you need a fix, an explanation, or a feature, a one-line summary at the top saves a round trip.
Response time and support hours
We are a volunteer-run education project rather than a staffed support desk, so we set expectations honestly. Routine questions are usually answered within one to three working days. Access problems that block an active exam window are treated as priority and are normally handled the same day. Requests that require research, such as a custom lab environment, a bulk track question, or a sponsorship conversation, can take up to two weeks. We do not operate a 24x7 on-call rota, and we would rather tell you that up front than leave you waiting on a reply that will never come overnight.
Published support hours: messages are monitored on a best-effort basis across the working week. Urgent access issues are prioritised; routine questions may take up to three working days to answer.
Other ways to get help
Before you write, it is worth checking the frequently asked questions, which covers account setup, XP and ranking, lab access, and the most common troubleshooting paths. The field guides contain full walkthroughs for popular scenarios such as subnetting, OSPF neighbour troubleshooting, VLAN trunking, and packet capture, and the resource library holds command references and cheat sheets you can keep open while you work.
If you are an instructor, a student representative, or a security community organiser who wants to use ByteBreach material in a classroom, tell us about the context and we will point you at the public guides and the editorial policy that explains what you may reuse and how to attribute it. We are generally happy to support classroom use when the attribution is clear and the material is not resold.
Reporting a security issue in ByteBreach
If you believe you have found a vulnerability in the platform itself, please report it privately through the form and mark the subject as a security disclosure. We will acknowledge the report, reproduce it in an isolated environment, and tell you what we plan to do. We ask that you do not run exploit tooling against other learners, avoid publishing proof-of-concept details publicly before a fix is available, and give us a reasonable window to release a patch. We do not offer monetary rewards, but we will credit you in the release notes if you would like to be named.
For advertising, sponsorship, or partnership enquiries, please use the same form and choose the appropriate subject. Note that we do not sell, rent, or share personal data with advertisers, and we do not accept payment for placement of deceptive, unlawful, or misleading creative. Our full advertising position is set out in the Terms and Conditions and the Privacy Policy.
