Private assessment
Request an assessment of a domain you own.
The public edition is deliberately limited to five reserved test domains. For real infrastructure, an assessment is arranged directly: reviewed manually, authorised in writing, and reported with the same evidence standard you can inspect in the sample report.
Most straightforward domain assessments are delivered within 3–5 business days after scope and written authorisation are confirmed. You receive an evidence-backed score and grade, prioritised findings, and the report in HTML, JSON, CSV and TXT formats.
The final price depends on scope. No payment is taken and no scan starts until the scope, authorisation, timing and price are agreed in writing.
Assessment request
reviewed manuallyThis form is a request, not a scan trigger. Submitting it does not cause any lookup, probe or assessment to run against the domain you enter.
What happens next
- A person reads the request — there is no automated pipeline
- Ownership or authorisation is confirmed
- Scope, timing and format are agreed in writing
- Only then does an assessment run
What not to send
No passwords, no private keys, no customer data. A domain name, a company name and a description of the concern are enough to start the conversation.
Prefer email?
Write to myself.atiff@gmail.com with the domain and your authorisation context.
The process
Four steps, and the first one is a human reading your request.
The restriction that makes the public demo safe is also why a private assessment is arranged rather than self-served.
You send the request
Company, domain, contact email, a short description of what you want to understand, and a confirmation that you own the domain or are authorised to request an assessment of it.
It is reviewed by hand
Nothing is scanned automatically. Requests are read, and domains are checked against the authorisation you describe before any work is agreed.
Scope and authorisation are agreed
Written authorisation, the controls in scope, the window in which the assessment runs, and the report format are confirmed in writing.
The assessment runs and you receive a report
Read-only external checks against the agreed scope, delivered as a report with the score, grade, findings, evidence and the consent record.
What an assessment covers
The full 22-control catalog: DNS integrity, email authentication, transport security, browser headers and network exposure. The public sandbox demonstrates eight of those controls on reserved domains; a private assessment covers the agreed scope for your infrastructure.
- External and read-onlyNo credentials, no exploitation, no payloads, no internal access.
- Evidence per findingEvery conclusive result quotes the observation that produced it.
- Multiple formatsHTML for reading, JSON for tooling, CSV for tracking, TXT for tickets.
- Consent documentedA hash-chained consent receipt is embedded in the report.
What it is not
An assessment is not a penetration test, not a compliance certification and not a guarantee that a business is secure. It reports what is observable from outside, with evidence, and states the limits of that view in the report itself.
Read the limitationsQuestions before you request?
The FAQ covers authorisation, scope, report formats and what happens to your data.