Confidential assessment request
Describe the system, concern, and outcome you need.
Send enough non-sensitive context to identify the right engagement and next scoping step. Do not include passwords, private keys, backup archives, confidential source code, or other secrets.
Never send credentials, private keys, backup archives, or confidential source code through this website.
- security@wpserverguard.com
- Initial reply
- Same business day for an active incident; otherwise within 24 hours
- First message
- Non-sensitive scope and business context only
- Access
- Arranged after scoping through an agreed secure method
- Testing
- Begins only after written authorization
Assessment request
Four short steps. Nothing in them asks for a password.
Pick what you are seeing and where the site is hosted, say who the reply should go to, and send. Once you pick a symptom the message is optional, so a hacked or suspended site can be reported in under a minute. Everything goes directly to security@wpserverguard.com.
- Each symptom says what is useful to write, and which guide to read while you wait
- You do not need panel, FTP or WordPress access to send this, even if the host has suspended the account
- Access is arranged only after a written scope, through a one-time link you create
What happens next
Scoping comes before access
- 01
Initial reply — same business day for an incident, otherwise within 24 hours
Clarify the objective, system boundary, urgency, and any information needed to choose the engagement.
- 02
Written scope
Document systems, access, exclusions, testing constraints, deliverables, fee, and authorization.
- 03
Secure access
Agree a secure exchange method and create temporary least-privilege access where required.
- 04
Begin work
Start within the agreed window with named contacts and escalation procedures in place.