Subdomain has an unclaimed-hosting fingerprint
ShipReady found a configured subdomain whose response matches a supported hosting-provider unclaimed-resource fingerprint.
Why it matters
A stale third-party hostname should be reviewed promptly because a provider resource that is no longer claimed may be able to be claimed by someone else.
How ShipReady detects it
What it inspects
ShipReady follows supported DNS relationships for configured subdomains and fetches bounded HTTP and HTTPS responses. It compares response text with provider-specific unclaimed-resource fingerprints.
What triggers a finding
The rule triggers when a configured target and a supported provider fingerprint match the scanner's takeover condition.
What the evidence shows
The observed subdomain configuration and response match a provider-specific fingerprint used by the scanner for a potential unclaimed resource.
Limits of this check
ShipReady does not attempt to register a provider resource, authenticate to the provider, claim the hostname, or demonstrate content control. A fingerprint is a potential-condition signal, not confirmation that a takeover has occurred or can be completed.
How to fix it
Verify the provider resource ownership
Check the DNS record and the associated provider account to determine whether the hostname is still intentionally claimed.
Remove stale DNS or restore the intended claim
Delete an unused record or claim and configure the intended provider resource before the hostname is used again.
How to verify the change
Confirm both sides of the mapping
Recheck DNS and the provider account after remediation, then verify that the fingerprint is no longer served.
Expected: The hostname is either removed or points to a resource controlled by the organization.