Dashboard

Overview of your phishing simulation campaign

Recipients
0
Emails in list
Emails Sent
0
Campaign launched
Link Clicked
0
Opened phishing link
Credentials
0
Entered username/password
Click Rate
0%
Of total sent

Click rate breakdown

Clicked link 0%
Submitted credentials 0%
Not clicked 100%

Quick actions

Recent activity

Event Email / Name IP Address Timestamp (PHT)
No activity yet. Launch a campaign to start tracking.

Recipients

Manage the staff who will receive the phishing simulation email

Recipient list

Name Email Department Status Actions
No recipients yet. Add staff emails above.
0 recipients

Campaign

Configure your phishing simulation email and launch the campaign

Sender configuration

💡 You need an SMTP service to actually send emails. We recommend Gmail App Password, Brevo (free), or Mailgun. Enter SMTP settings below.

SMTP settings

Phishing link

Each recipient gets a unique link: phishUrl/?rid=UNIQUEID

Email body (HTML)

Preview
HTML Source

Launch campaign

Send to 0 recipients using the email configured above.

⚠ Since this runs in the browser, emails are sent via a Cloudflare Worker relay or you can download the recipient list and use a desktop mail client / external SMTP tool.

Results

Real-time tracking of who clicked and submitted credentials

Visited
0
Clicked the link
Submitted
0
Entered credentials
Safe
0
Did not click
Submission rate
0%
Of total recipients

Activity log

Event Name Email Department Username entered Password entered IP Timestamp (PHT)
No results yet. Results appear here when recipients click your link.

Manual log entry

Since email sending runs externally, paste tracking data from your Cloudflare Worker KV dashboard here, or manually log when someone reports clicking the link.

Paste JSON from Cloudflare KV

Copy the KV data from your Cloudflare Worker dashboard and paste it here to import all tracking records at once.

Settings

Configure dashboard access and campaign options

Dashboard access

Data management

Deployment guide

This dashboard — upload this HTML file to Cloudflare Pages as index.html. All data is stored in your browser's localStorage.

Phishing clone page — deploy lime_eportal_login.html as a separate Cloudflare Pages site (e.g. e-portal-lime-elnido.pages.dev).

Tracking Worker — deploy worker.js + KV binding as a Cloudflare Worker. It logs visits and submissions, then redirects to the awareness page.

Email sending — use Gmail App Password with an SMTP relay worker, or export the recipient CSV and send via your preferred mail client (Outlook, Thunderbird, etc.).