Type at least two letters.

    ↑ ↓ to moveEnter to open

    The passive audit

    What the current audit reads from a website, what it does not do, and what it cannot see.

    Updated

    The live audit profile is passive. It reads a website the way a visitor’s browser, a search engine or a mail server would, and nothing more. Its version is recorded on every run (profileVersion), so a result always says which profile produced it.

    What it reads

    For each run:

    • The page, once, with its response headers. Redirects are followed one by one, at most five, and every address on the way is checked against the address rules.
    • The plain http:// address, to see whether it moves visitors to https://.
    • robots.txt, the sitemap and security.txt: small public files that most sites publish.
    • Public DNS records of the domain: addresses, mail servers, SPF and DMARC policies, CAA and DNSSEC.

    That is about ten small requests per run. The page read stops at 1.5 MB or 10 seconds.

    What it never does

    • It does not sign in, fill in forms or click anything.
    • It does not scan ports, guess paths or try known exploits.
    • It does not run the page’s JavaScript in a browser.
    • It does not send more than one audit at a time to the same site.

    The owner of an audited site sees a few ordinary requests in their logs, nothing more.

    The areas it covers

    Area Looks at, in broad terms
    Availability Does the site answer, over HTTPS, without a redirect chain?
    Security The security headers and cookie flags a browser gets, and the domain’s security records.
    Email Whether the domain receives mail and protects it with SPF and DMARC.
    Performance The basics visible in one page read: response time, size, compression, blocking scripts.
    Marketing Search and sharing basics: title, description, canonical, robots, sitemap, social tags.
    Accessibility Basics visible in the HTML, for example the page language and image text.
    Privacy Signals a visitor’s browser receives on the first load.
    Technology What the site is built with, as far as it shows.

    Signed in, the app lists every check of the profile with what it means under What is checked. The same catalogue is available over the API at GET /rules.

    What it cannot see

    A passive read has limits, and the report says so instead of guessing. These show as Not tested, never as a failure:

    • the TLS certificate’s expiry date,
    • DKIM, because its selector is not public,
    • anything behind a sign-in.

    Performance findings come from one read of the page from Metricevo’s servers. They are not lab measurements in a browser and not real-user data.

    Results are observations

    Every result says what was seen and how sure it is (confidence). Privacy results are technical observations, not legal advice or a certification of compliance.