Search Keywords
Domains the corpus lists that look like a brand or domain: typosquats, homoglyphs, the name on other TLDs or wrapped in phishing words (paypal-login). A bare keyword is read as its .com; the searched name itself comes first when listed. Most dangerous first, capped at 500 hits (total_hits counts every lookalike found).
Path parameters
Search keywords (e.g., 'paypal', 'microsoft')
Response
Search results response (capped at 500 hits)
Example response
{
"keywords": "paypal",
"matches": [
{
"domain": "paypa1.com",
"fuzzer": "homoglyph",
"threatLevel": "critical"
}
]
}Changes
Changed in 2 of the 15 revisions of this API.73
- ○
added the non-success response with the status
response-non-success-status-added
- ○
added the required property
to the response with the statusresponse-required-property-added
- ○
added the required property
to the response with the statusresponse-required-property-added
- ○
- ▲
the response property
became nullable for the statusresponse-property-became-nullable
- ▲
the response property
became nullable for the statusresponse-property-became-nullable
- ▲
the response property
became nullable for the statusresponse-property-became-nullable
- ▲
the response property
became optional for the statusresponse-property-became-optional
- ▲
the response property
became optional for the statusresponse-property-became-optional
- ▲
the response property
became optional for the statusresponse-property-became-optional
- ▲
the
response's property format changed fromint32toint64for statusresponse-property-type-changed
This revision also has 17 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲