Skip to content
Explore the preview
Browse workflow ideas

Understand your public domain footprint and keep reconnaissance in scope.

Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.

For a domain the organization owns or is explicitly authorized to assess, collect passive subdomain and public DNS information and prepare a structured report for the security team. Keep the target scope documented, avoid active probing or exploitation, treat records as time-sensitive clues rather than proof of a vulnerability, restrict report access, and require a qualified owner to validate findings before remediation.

Explore the simulation Explore the idea

Actual availability depends on published steps, supported connections, permissions, and provider approval.

Illustrative workflow and outcome
An authorized security review beginsA verified domain, written assessment scope, and approved report recipients
“Review public domain records without crossing into unapproved testing or exposing sensitive findings.”
Work through the request.

Clear tasks, with review where it matters.

  1. Verify domain ownership and written scope
  2. Collect passive public records
  3. Prepare a dated, source-linked report
See all 5 tasks
A dated domain inventory and DNS summary with validation notes and security-owner review status.

What this workflow could do

Helps a security team gather public subdomain and DNS records into a report for an authorized review.

Review points proposed in this idea

Public records can be stale, incomplete, or misinterpreted, and security details can create risk if widely shared. Restrict the review to owned or approved domains, keep it passive, verify records with the system owner, and do not treat a report as authorization for further testing.

How the idea could work

Select an illustrative task to explore its proposed role. No workflow runs here.

Explore the sequenceStep 1 of 5

  1. Confirm the exact domains and records the reviewer is authorized to examine.

Step 1 of 5

Verify domain ownership and written scope

Confirm the exact domains and records the reviewer is authorized to examine.

Proposed setup considerations

These are planning notes for the concept, not instructions for a currently available template.

  1. 01

    Record approved domains and assessment purpose

    Keep target scope, authorization, and review contacts documented and current.

  2. 02

    Keep collection passive and proportionate

    Do not expand into probing, exploitation, or unrelated domains without separate approval.

  3. 03

    Protect reports and recipient lists

    Limit security inventory access to people responsible for the assessed environment.

  4. 04

    Set validation and remediation ownership

    Assign a security owner to verify findings and approve corrective actions.

Read the prelaunch status

Published templates and verified customer availability remain pending.

A little help with the whole task

A little less busywork.
A little more room for you.

Explore the sample experience while launch details are being finalized.

View pricing status Explore the simulation