Alerts and channels
The daily email, the changes that alert, and the Slack, Teams, PagerDuty and webhook channels that carry them.
Updated
How you are told
- Findings list
- New findings appear in the findings list as they are found, on every plan.
- Daily email digest
- One email a day at most, only when something new matched. Never one email per match. Every plan.
- Alert channels
- Slack, Microsoft Teams, PagerDuty or a signed webhook, sent as each alert happens. Paid plans.
- Weekly breach brief
- Optional weekly email of new public breach disclosures in the sectors you pick, across all companies and not matched to your domains. Off until you turn it on. Paid plans.
- Free
- Findings list and daily digest
- Pro
- Findings list, digest and up to 5 channels
- Business
- Findings list, digest and up to 5 channels
- MSP
- Same as Pro
The digest switch, the breach brief and the channels are under Alerts in the top bar, beside a list of the changes that send an alert. Settings links there.
The daily digest
The digest is on when you sign up. Turn it on or off with Daily email digest under Alerts, then Save. It goes out at most once every 24 hours, counted from your last one, and only when there is something new.
It lists up to 8 lookalikes, highest risk first, each with:
- the domain written with
[.]and never linked, so it cannot be clicked by mistake; - why it is in the email when it is an older finding that changed: “now accepts mail”, “now has a login page”, “got its first certificate” or a page that now looks like your site;
- its risk and evidence labels;
- an Open link to that finding in your dashboard.
Then a count of weak matches and of parked lookalikes, up to 10 new hosts on your own domains, and a Review in dashboard button. Dismissed findings are left out.
The weekly breach brief
Under the digest, Weekly breach brief turns on a Monday email of breach disclosures newly published by FinSecLedger, MedSecLedger and EdSecLedger. Tick Finance, Healthcare or Education to pick the sectors; all three are ticked when you first turn it on. Changes save as you make them. Nothing is sent in a week with nothing new.
The disclosures are for all companies in those sectors and are not matched to your domains. It is part of Pro and MSP: on a free account the switch is shown locked. If Pro ends while it is on, it shows as paused and can still be turned off. See the weekly breach brief for what the email contains.
Which changes alert
Every finding is re-checked about once a day and the changes are recorded in its history. These alert:
| Alert | Sent when | Plans |
|---|---|---|
| New lookalike | A new finding above its alert threshold, or one whose score rose | All |
| Went live | A parked or empty lookalike now serves a site or accepts mail | All |
| Now accepts mail | A lookalike that was already up gained mail servers | All |
| Now has a login page | A password field appeared on its page | All |
| First certificate | A lookalike found before it had a certificate got its first one | All |
| Page looks like your site | A screenshot comparison matched on look or icon | Paid plans |
Moving address, changing nameservers, going down and coming back are recorded in the history but do not alert. An entry on a public phishing list raises the finding’s risk but is not a change in its history and does not alert on its own. When going live alerts, the mail and login page that came with it are part of that one alert.
The seven-day quiet window
A lookalike alerts at most once per kind of change in seven days. A domain that goes down and comes back, or flips its mail records, does not alert every time. A dismissed finding never alerts.
Alert channels
Add channels under Alert channels in the Alerts view, up to five per account. Each row shows its last result, for example “Last send OK (HTTP 200)”, and has Test, Disable and Delete. Tests are limited to five an hour.
- Slack
- Create an incoming webhook for the Slack channel and paste its URL (https://hooks.slack.com/…).
- Microsoft Teams
- Add the "Post to a channel when a webhook request is received" workflow in Teams and paste its URL.
- PagerDuty
- Add an Events API v2 integration to a service and paste its 32-character integration key. PagerDuty is paged only when a lookalike goes live, starts accepting mail or gains a login page. Going live and a login page open a critical incident, mail a warning. New findings, first certificates and page matches are not sent to it.
- Webhook
- A URL of your own, preferably HTTPS. Private and internal addresses are refused. Each delivery is signed, and the signing secret is shown once, when the channel is added or a new one is generated.
In Slack and Teams the lookalike is always written with [.], so the chat client does not turn it into a link or preview it.
Delivery, retries and signatures
A delivery that times out, cannot connect, or gets a 429 or 5xx answer is retried twice, after 2 and 10 seconds. Other errors are not retried. A delivery that fails all three attempts is dropped; the finding is still in your findings list and the digest. After 20 failed deliveries in a row the channel is turned off and shows Disabled after repeated failures, with a button to turn it back on.
Webhook payloads, headers, the signature scheme and a verification example are in the API reference.
Channels saved while on Pro are kept but not used while the account is on the free plan.
Limits
- Changes are found by periodic checks, so an alert follows a change by up to about a day.
- Retries happen within a few seconds of the first attempt. A delivery is not queued for later.
- An alert says what was observed. It is not a verdict that the site is malicious.
- If an email to your address is refused permanently by your mail server, or is marked as spam, we stop sending GreyPhish emails to that address: the digest, the weekly report, the breach brief and client reports. Password reset emails still arrive. To get them back, fix the mailbox or change the address on your account, or contact us at admin@greyphish.com.