C
CertPilot

Sample reports

Inspect the deliverable before you sign up.

Static, fictional examples of every real CertPilot report format. Review the current public sample PDFs, source boundaries, and report structure before adding your own data. Nothing here is a live customer account.

Fictional demo dataSix formats · static PDFs · reports generated on demand

Featured report

Governance Evidence Pack

The format that best represents the platform: public checks and customer-maintained registers brought into one dated cross-module summary.

C

Governance Evidence Pack

Demo / illustrative
Period
Demo period
Scope
Demo workspace
Source
Checks + registers
01

External footprint — SSL, DNS, RDAP

Observed
02

Email authentication coverage

Example gap
03

Renewal risk register

Review
04

Access review completion

Current
05

Vendor status context

Observed
Fictional workspace · no customer data

Supporting formats

Five more real report formats.

All fictional demo data

Two focused formats lead as ReportCards; the other three become compact rows so the gallery has hierarchy rather than six identical blocks.

ReportFormat / 02

Domain Health Report

Shows that public-facing domains are actively checked for SSL certificate, domain-registration, DNS, and email-authentication evidence, with issues surfaced for review.

On demand

ReportFormat / 03

Renewal Risk Report

Shows upcoming and overdue renewal risk alongside owners, dates, notice windows, open decisions, and incomplete records that need follow-up.

On demand

04

Monthly Proof Report

Shows a dated monthly summary of domain health, email-authentication evidence, renewal risk, DNS changes, and access-review counts.

Generated on demand for a monthly period

05

Weekly Governance Report

Shows a short governance snapshot of recent domain, certificate, DNS, renewal, and access-review signals that need review.

On-demand only — no automated weekly delivery

06

Access Review Register

Shows a dated register of access records, review states, reviewer context, and the follow-up still required at sign-off.

On demand after review sign-off

Where reports come from

Every section traces back to a check or a register.

Reports are assembled from public-signal results and customer-maintained records. The source category and scope remain visible so the reader can understand the basis and limits.

Checks · public signals

Observed outside

SSL, DNS, email authentication, RDAP, and official vendor status.

→ Domain Health · public-signal sections

Registers · maintained

Recorded by your team

Renewals, people, assets, systems, access reviews, decisions, owners, and sign-off.

→ Renewal Risk · access-review sections

Evidence · output

One dated artifact

Both inputs brought into a readable report with scope and limits stated.

→ Governance Evidence Pack

Domain Health workflow today

What the live evidence flow can include.

01

Technical domain health

SSL status and expiry, domain/RDAP registration expiry where available, DNS records, and an overall status per domain.

02

DNS change evidence

The latest public DNS snapshot plus what changed between checks. This is read-only evidence, not DNS restore.

03

Domain Governance Review

Customer-entered owner, purpose, lifecycle status, renewal decision, and last-reviewed date beside the automated checks.

04

SSL readiness

Customer-entered management method, automation status, and readiness notes. CertPilot does not issue or renew certificates.

05

Email sending sources

A customer-entered register of systems that send mail from a domain. CertPilot does not scan mailboxes or send email.

06

Management-ready evidence

A dated summary for management or client review. It is operational evidence, not certification or an audit guarantee.

How reports are generated

Checks and records, assembled on demand.

CertPilot checks monitored domains daily. SSL evidence comes from a live TLS handshake; domain-registration expiry comes from RDAP; DNS and email-authentication evidence comes from public DNS records. Renewal, people, assets, systems, and access-review evidence comes from registers your team enters or imports.

Each report uses the inputs relevant to that format. Generate the next dated snapshot from the dashboard when you need it; there is no automated Weekly Governance delivery or connector-enriched report data.

What a report is not

Evidence — not a certificate.

A report is

  • A dated record of what was checked and reviewed
  • Scoped, with sources and limits stated
  • Assembled from public signals and customer-maintained records
  • Something a person can read, question, and act on

A report is not

  • A compliance certification
  • An audit guarantee or professional sign-off
  • A vulnerability scan or penetration test
  • An uptime monitor
  • Employee monitoring or private-content inspection
  • A connector read from Microsoft 365, Google Workspace, or an identity provider
  • Legal advice

Demo reports use fictional data. Live reports document operational evidence; they do not certify compliance or replace an auditor's judgement.

From sample to your own

Generate evidence from your own checks and registers.

Add the domains and maintained records each report needs, review the current evidence, and generate the relevant format on demand.