Site map
Every page on ZNetLab · last checked 3 October 2026
This is the readable one. sitemap.xml is the same site for crawlers — a flat list of indexable addresses with no explanation — and robots.txt says what they may fetch. Two badges below mean what they say: sign-in needs an account, and not indexed is a page kept out of search on purpose and listed here for a reader.
The product
What each one installs, what images it runs and what it costs — including which of them to use when the answer is not this one.
The browser simulator end to end: the workspace, two worked labs, devices, consoles, the PC desktop and packet capture.
The lab platform: booting real images, consoles and terminals, capture and the conversation view, the operations screen, and which images you can run.
Every article, blog post, answered question and browser lab that has cleared moderation — each at an address of its own, readable without an account. This index is generated from what is published rather than written here, which is why it is the one entry on this page with no file behind it.
How people set challenges for each other, earn points and ranks, ask for help, run a study group that writes its own exam papers, and share what they study from — with every screen, every rule and every endpoint.
Loading images, licences, accounts and the server itself. Fetched from the server for administrators only.
Learn — the teaching site
/learn/ is a single page. The sections below are views of it rather than separate documents, which is why the crawler's sitemap lists the one address and no fragments.
- Home — what is new
- Lab catalogue — every lab, by subject
- Articles — written explanations
- Blogs — posts from members
- Forums — questions and answers
- Security — the security subject
- Pricing — the teaching tiers
- Contact — reaches a person
- Contribute — write a lab or an article
What comes OUT of it has real addresses. Articles, blogs, forums and labs are views of this one page while you are signed in and reading the feed; each published item also has a page of its own under /read/, with its own title, its own description and its own place in the crawler's sitemap. Those are generated from the content store at the moment they are asked for, so the list is never a deploy behind.
The applications
These are tools rather than pages: there is nothing to read on them until somebody signs in, which is why they are not in the crawler's sitemap.
Build a topology and configure it in the browser. No server, no images.
Real images on a real server: Dynamips, IOL, QEMU and the built-ins, with consoles and packet capture.
What is broken, where it is, and who got in — for the network you are running.
Every account on the server, managed like a directory: the tree, the list, companies, groups, admin roles and the support queue. It used to be a page of its own at /accounts, and companies had a second one at /org; both now redirect here.
Inside the lab platform, for administrators: everything running, accounts, orders, support, moderation, images, licensing, the catalogue, the readiness check, the activity trail, host health, security, analytics — and Marketing, the plan for getting this site found.
Policies
Which document answers which question — one row per thing people actually ask, linking straight to the section that answers it.
What ZNetLab is, your account, acceptable use, uploaded images, payments and liability.
What is stored, what the browser keeps, how long, and what you can ask us to do.
The open-source components ZNetLab ships, and the trademark position on the vendor software it does not.
Documents
Long-form guides and reports. Every one of these carries noindex on purpose —
they duplicate material the guide covers, and indexing both splits the ranking of one
subject across two pages.
The whole lab platform in one document, with a PDF beside it.
What a server needs, and how real images are run on it.
Getting to a ZNetLab server on your own network.
For machines
- sitemap.xml — the indexable addresses
- robots.txt — what may be fetched
If a page you expected is missing from this list, it is missing from the site — the list is checked against what is actually served. The contact page reaches a person.