Docs

Why domain verification matters

Shieldome sends benign but active probes - injection payloads, SSRF and path-traversal tests - to find real vulnerabilities. Those are unsolicited requests to a live site, so Shieldome only runs them against a target your account has proven it controls. Until a domain is verified, a scan of it runs in passive mode.

Passive vs active assessment

TierRuns onWhat it checks
PassiveAny public targetSecurity headers, TLS/SSL, certificates, DNS and email records, technology fingerprint, exposed files, external and dark-web intelligence, performance
ActiveVerified targets onlyInjection probing (SQLi, XSS, path traversal, command injection, SSTI, SSRF, XXE, LDAP, NoSQL, CRLF, parameter pollution) and the opt-in active-exploitation checks
ℹ️
A scan of an unverified domain still returns a full passive report and an overall grade. The active checks appear as the coverage finding "Active and Injection Checks Require Domain Verification", not as "secure" - they were not run, which is different from "no vulnerability found".

Verify a domain

  1. Open the account menu: click the ⋮ button next to your name at the bottom of the left sidebar.
  2. Choose Authorized Sites.
  3. Enter your domain, confirm you are authorised to scan it, and click Add.
  4. On the domain's row, click Verify.
  5. Choose DNS TXT (recommended) or file verification.
  6. Publish the record or file shown, then click Check Now.

DNS TXT method (recommended)

Add this TXT record at your DNS provider. The token is generated per domain when you click Verify:

DNS TXT record
Name:  _shieldome-verify.example.com
Type:  TXT
Value: shieldome-verify=<your-token>

DNS changes can take up to 24 hours to propagate, though most providers update within minutes. Click Check Now once the record is live.

File method

If you cannot edit DNS but can publish a file, host this file over HTTPS instead:

verification file
URL:      https://example.com/.well-known/shieldome-verify.txt
Contents: shieldome-verify=<your-token>

What a verified domain covers

Verifying a domain also authorises every subdomain under it. Verifying example.com lets you run the full active assessment against app.example.com, api.example.com and the rest, without verifying each one separately.

IP targets and the WordPress plugin

  • IP addresses. A bare IP or CIDR range cannot be verified with a DNS TXT record, so scans of an IP run in passive mode. To authorise an IP range for active testing, contact [email protected] with proof of control.
  • WordPress plugin. The Shieldome plugin triggers a SaaS scan of your site. Verify your site's domain once under Authorized Sites to get the full active assessment from the plugin too; until then the plugin's scans are passive like any other unverified target.
💡
Only getting passive results? That is the expected behaviour for an unverified target. Verify the domain as above and re-scan to run the active injection checks.