Verifying Deployment

After deploying LobsterHoney -- whether via beacon or proxy mode -- verification confirms that your traps are accessible and detection signals can flow back to the dashboard. Traps that are not reachable cannot protect your site.

Beacon Verification

Beacon verification checks that the beacon script is loading correctly on your site. From the Deploy page, click Verify to run an automated check. The verification tests:

• The beacon script URL is reachable
• The script loads without errors
• Callback signals can be sent back to the detection server

A green checkmark indicates your beacon is live and working.

Proxy Verification

Proxy verification is more detailed. It tests each trap path individually and the callback route. For each configured path, the check confirms:

• The path responds with a 200 status (not 404 or 502)
• The response contains valid trap content
• The /api/callback route is forwarding correctly

Results are shown per-path, so you can see exactly which paths are working and which need attention.

Manual Testing

You can also verify your deployment manually using curl. Replace the domain and org slug with your actual values:

A successful response returns trap content with a 200 status code. Check your dashboard -- a new session should appear within seconds.

What "Verified" Means

The Verified badge on the Deploy page means all configured trap paths and callback routes passed their most recent verification check. Verification runs on-demand when you click Verify. If you change your proxy configuration or DNS settings, re-verify to confirm everything still works.

See Also

• Beacon Setup -- deploying via script tag
• Proxy Mode -- proxy deployment with per-path verification
• Dashboard Overview -- monitoring detections after deployment