In this article:
When adding a subdomain (ex: zzzz.apexdomain.com) via the Digital Footprint, the following error is returned: Something went wrong. Bad Request: zzzz.apexdomain.com: eTLD+1 is only supported.
The ability to automatically add subdomains via the Digital Footprint is not currently available in the platform.
You may submit a Support ticket mentioning the subdomains to add. If requirements are met, our Support team will proceed to the addition.
For a subdomain to be present on the digital footprint page, the subdomain must meet the following requirements:
- The subdomain's apex domain must be in the Digital Footprint.
- The subdomain has an 'A record'.
- The IP addresses resolved to the subdomain must already be attributed in the Digital Footprint
The attribution for subdomains works the following way:
Subdomains ===linked with==> Apex domain ===attributed to==> Scorecard
A subdomain is not linked to a scorecard, it is linked to its apex domain. It also means that a subdomain can only be present on a scorecard if its apex domain is present also on the scorecard, and be present in the Digital Footprint if its IPs can be attributed to the scorecard.
Note: SecurityScorecard will only display subdomains on Digital Footprint up to the eTLD+2 (effective top level domain). An example would be: example2.example.com could be shown, but not_valid.example2.example.com would not be shown.
Subdomains cannot be force removed from the Digital Footprint. Subdomains are related to their apex domain, so from SecurityScorecard perspective, they belong to the same scorecard. If the apex domain is on the scorecard, all its subdomains will also be present. If the apex is not on the scorecard, all its subdomains will also not be present.