Detection sources and lookalike types
Greyphish finds lookalikes in certificate logs, ICANN zone files and DNS checks, and labels each by how it imitates your domain.
Updated
Where detections come from
- Certificate Transparency (CT)
- Publicly trusted TLS certificates are recorded in public logs. Greyphish reads the logs as certificates are issued and checks each name against your watched domains, so a match appears on your dashboard soon after the certificate is logged. A lookalike usually needs a certificate before it can host a convincing page.
- ICANN zone files (CZDS)
- Lists of the domains registered under the generic endings Greyphish is approved for through ICANN's Centralized Zone Data Service. Once a day each file is compared with the day before, and the names that newly appeared are checked against your watched domains, released through the day rather than all at once. A registration with no certificate is usually seen within about a day of appearing in a zone file.
- DNS check (DNS)
- When you add a domain, Greyphish looks up which of its generated lookalikes are already registered, and repeats this every 30 days. This catches lookalikes registered before you started watching, and ones under endings with no zone file.
- Certificate siblings (CERT)
- Other registered domains on a certificate for one of your findings. They are read from the certificate when Greyphish sees it in the logs. For a finding whose certificate Greyphish did not see that way, such as a zone-file finding or an older one, they are looked up on crt.sh, a few at a time. A CDN's shared certificate is left out, and one naming more than 20 registered domains keeps only the names that look like the same target. A sibling becomes a finding only when it scores at or above the alert threshold, and only when a certificate naming it was logged in the last 30 days; one seen only on older certificates is listed under Same certificate in the finding's Technical details but is not a finding of its own.
A new lookalike from the certificate logs is held back from alerts until a check of its certificate history confirms the host is actually new, so a long-standing name that renewed its certificate does not alert as new. A new certificate sibling is held the same way; if its history cannot be checked within 48 hours, it is released as new.
Kinds of lookalike
| Type | Example for acmelogistics.com | Level |
|---|---|---|
| Typosquat: a letter added, dropped, swapped, doubled or changed | acmelogistcs.com, acmeloigstics.com | medium |
| Homoglyph: characters that look alike, including Cyrillic letters in punycode names | acrnelogistics.com, or acmelogistics.com spelled with a Cyrillic а | critical |
| Combosquat: your name plus a word, a hyphen or a moved dot | acmelogistics-login.com, login-acmelogistics.com | high |
| TLD swap: the same name under another ending | acmelogistics.net, acmelogistics.co | high |
Each row in the findings list names the technique (Swap, Added word, Ending and so on), and the finding view explains it under Technical details, for example “two letters swapped”. An internationalised name is shown as it would appear in a browser, with the look-alike characters marked against your domain; its punycode form is the Defanged line under Technical details. Brand-plus-word combinations are only generated for names of 5 or more characters. A word joined to the front of your name without a hyphen scores below the alert threshold when the result reads as ordinary English: when the word runs into the start of your name (account + abilityworks reads as “accountability works”), or when your name is made of everyday words that follow it naturally (secure + thelantern, customer + carefield). Such a match is still listed, but never alerted on. The hyphenated forms, such as secure-thelantern.com, score and alert as usual.
Confidence and the alert threshold
Every match has a confidence score from 0 to 100%, shown under Technical details in the finding. For spelling variants it measures how close the name is to yours once look-alike characters are mapped back to the letters they imitate, so a homoglyph that is invisible to a reader scores close to 100%. A brand-plus-word name scores higher when the word is a suspicious one such as login, secure, pay or my.
| Kind of match | Alerts at or above |
|---|---|
| Spelling variant of your domain | 80% |
| Your name plus a word | 50% |
| Keyword or brand item (older accounts) | 50% |
| Host on your own domain | Never alerts |
A match below its threshold is still listed, marked “Scored below the alert threshold for its type”, and never alerts. It is most likely a different organisation with a similar name.
Likely yours
Some lookalikes are registered by the brand itself. Greyphish suggests a finding is yours when it uses the same nameservers as your domain (parking nameservers excluded), has the same registrant organisation (privacy services excluded) or redirects to your domain. The finding view says so under its verdict. It is a hint, not a decision: choose This is mine in the finding to move it to Dismissed. See dismissing findings.
Limits
- A lookalike resembles your domain. It is not necessarily malicious.
- Zone files cover only the generic endings Greyphish is approved for. Country-code endings such as .uk or .de are not in CZDS, so a lookalike there with no certificate is seen only by the DNS check, which can take up to 30 days.
- A finding first seen in a zone file reads “In zone files”, and its certificate row reads “None seen”. Once a certificate for it is logged, the certificate row reads “Seen in certificate logs” with that day, you are alerted to its first certificate, and first seen then reads “In certificate logs” with the original day. Zone-file findings saved before this was recorded keep the certificate-log label, because their source was not stored.