Licenses
This document is for Invicti Platform
Your Invicti Platform license determines how many targets you can set up for scanning. The total number of targets permitted is a combination of purchased FQDN targets and allowed target variations.
This document explains the nuances of how licensing works in Invicti Platform.
Refer to License management for details on reviewing your license usage.
What is an FQDN
A Fully Qualified Domain Name (FQDN) is the complete address of a specific system or host on the internet or within a network. It uniquely identifies a resource by combining:
- Hostname – The name of the specific server or system (e.g., www, api, or mail)
- Domain name – The registered domain associated with your organization (e.g., example.com)
When combined, these form the FQDN, such as www.example.com.

Refer to the Authorized target scanning policy for a list of Invicti test websites. These don't count towards the FQDN count.
Why are FQDNs not freed upon deletion
When you delete a target from your Invicti portal, the associated FQDN isn't immediately released back into your license pool. The licensing policy intentionally governs this and is designed to:
- Prevent license circumvention by repeatedly deleting and re-adding targets to bypass target limits
- Ensure predictable usage and billing over the subscription period
Key points:
- FQDNs remain active until your subscription period ends (license anniversary)
- Deleting a target only removes it from your dashboard. It doesn't reset license usage
- Targets (FQDNs) are tracked even after deletion

License behaviour differences
Full - Commercial - license
- You are allocated a fixed number of FQDNs per year (for example, 10 FQDNs for a 10-target license)
- You can exceed the allocation temporarily (up to ~120% of quota), but overuse is monitored and flagged
- Retired FQDNs are freed only at subscription renewal
- UI may not reflect exact usage due to retention of deleted targets (for example, showing 3/10 instead of 10/10 if 7 were deleted)
POC - Proof of Concept - license
- Hard limits are enforced: exceeding FQDN quota results in a blocking error
- No grace allowance beyond your quota
- If you receive a "Max FQDNs reached" error, this is expected behavior under a POC license
Exceptions for demo or testing
Demo targets or internal QA environments (e.g., temporary subdomains) may need flexibility. If your organization requires exceptions:
- Contact support and request adjustments for demo targets
- In some cases, your POC license can be swapped for a Full license to remove hard FQDN limits
Best practices
- Plan FQDN usage across environments (dev, staging, prod) to avoid hitting limits prematurely
- Tag and document test/demo targets for internal tracking
- Use target editing rather than deletion/re-creation to preserve your license allocation
- Request FQDN resets during renewal if prior targets are no longer in use
Need Help?
Our Support team is ready to provide you with technical help. Go to Help Center