Describe the redirect you already saw.

Keep the first observations

Note the original page address, approximately when it happened and whether it followed a search result, a bookmark or a direct visit. Record the device and browser. If you already have a screenshot, keep a private copy and remove personal information before sharing it.

Do not follow prompts to sign in, install software or download a file from the suspicious destination. Keep any browser security warning in place.

Note who has seen it

Say whether multiple visitors have reported the behavior or whether it has appeared only on one device or one route into the site. That difference is useful context; it does not by itself establish where the problem lives.

List recent events without assuming a cause

Record known website updates, new software, account changes and messages from the hosting provider. A recent change may help the investigation, but the timeline alone does not prove that it caused the redirect.

Keep incident information private

Raw logs, account exports and full site backups can contain private data. Mention that they exist rather than uploading them through the public inquiry form. The owner and reviewer can agree on an appropriate way to handle them later.

The WordPress incident guidance also recommends documenting observed symptoms and their timing when seeking help.

Send a short first inquiry

Contact Faith Forge Labs with the public website address, what happened and when you noticed it. Mention any host restriction and who can authorize a review.