Description
If an IP is available in the event (as parsed from the report or supplied by a domain resolver) the subscriber ID is set to that IP. If not, the event is marked as/stays unresolved.
Description
If an X-AbuseHQ-Resolve
header was set in the reported email its value will be parsed and subscriber ID, contract ID, and resolver data will be set.
Description
The most powerful resolver sends queries to a given endpoint and expects a response in a certain format. It will then set the subscriber ID, contract ID, and resolver data accordingly.
Attributes
Authorization: Bearer <token>
headerclient
is the subscriber id in the case that the event was resolved through some other resolver at an earlier point.Testing the Resolver
The front end offers a button to test the API resolver using some sample data, without having to take the configuration live. The request will come from the same IPs that they will come from in production.
18.193.183.51\
52.57.46.129\
18.158.191.233
Description
Allows setting a custom static ID to events going through this resolver.
Attributes
Description
If the report contains email evidence and that email contains a from header its value will be used as the subscriber id.
Description
If a domain or URL was parsed from the report it will be used to extract a domain. Further post-processors can then change the extracted value.
Attributes
resolve_to_ip
processor is available. It allows resolving extracted domains to an IP by doing a DNS lookup. Note that the DNS records might have changed since the abuse incident happened and thus the resolved IP might not be correctly identifying the source of abuse that is reported.Description
If the report contains email evidence and that email contains one of the given headers its value will be used as the subscriber id. The headers will be checked in the given order and post-processors will be applied after value extraction.
Attributes
Description
If the report contains email evidence and that email contains one of the given headers its value will be used as the subscriber id. The headers will be checked in the given order and post-processors will be applied after value extraction.
Attributes
Description
If an IP is available in the event (as parsed from the report or supplied by a domain resolver) the subscriber ID is set to that IP. If not, the event is marked as/stays unresolved.
Description
If an X-AbuseHQ-Resolve
header was set in the reported email its value will be parsed and subscriber ID, contract ID, and resolver data will be set.
Description
The most powerful resolver sends queries to a given endpoint and expects a response in a certain format. It will then set the subscriber ID, contract ID, and resolver data accordingly.
Attributes
Authorization: Bearer <token>
headerclient
is the subscriber id in the case that the event was resolved through some other resolver at an earlier point.Testing the Resolver
The front end offers a button to test the API resolver using some sample data, without having to take the configuration live. The request will come from the same IPs that they will come from in production.
18.193.183.51\
52.57.46.129\
18.158.191.233
Description
Allows setting a custom static ID to events going through this resolver.
Attributes
Description
If the report contains email evidence and that email contains a from header its value will be used as the subscriber id.
Description
If a domain or URL was parsed from the report it will be used to extract a domain. Further post-processors can then change the extracted value.
Attributes
resolve_to_ip
processor is available. It allows resolving extracted domains to an IP by doing a DNS lookup. Note that the DNS records might have changed since the abuse incident happened and thus the resolved IP might not be correctly identifying the source of abuse that is reported.Description
If the report contains email evidence and that email contains one of the given headers its value will be used as the subscriber id. The headers will be checked in the given order and post-processors will be applied after value extraction.
Attributes
Description
If the report contains email evidence and that email contains one of the given headers its value will be used as the subscriber id. The headers will be checked in the given order and post-processors will be applied after value extraction.
Attributes