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
- 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
Send the request through this form.
Every field goes directly to security@wpserverguard.com. Context that helps with the first reply:
- Domain and whether the site is production, staging, or currently offline
- Relevant symptoms, warnings, deadlines, and business impact
- Number of WordPress sites, servers, environments, or custom components
- Whether you control WordPress, hosting, DNS, source, logs, and backups
- Desired outcome: assessment, cleanup, report, remediation, retest, or continuing care
What happens next
Scoping comes before access
- 01
Initial reply — 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.