feat: Add verification details for some common crawlers #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds reverse dns verification details for common crawlers.
I chose to add
verification
as a list so that it can be present on all bots, regardless of whether we can verify or not.When we add cidr validation in the future we will add it as a second option to those bots that support it, we can then just add logic to prefer cidr validation for bots that support both.
I think its nice to have both so that this JSON will show a full picture of everything that a crawler supports.
The mask can contain two types of wildcard:
@
matches zero or more characters*
matches zero or one characterBy supporting both types of wildcard we can implement validation exactly how each bot provider specifies in their docs.