Testing authorization

Fabereye Cybersecurity tests only targets that the customer is authorized to test. Domain control must pass a live DNS TXT or HTTPS file check before payment and again before the separate testing service starts. Document-based ownership checks are not accepted.

What you must provide

• Each exact hostname or FQDN. A root domain does not automatically authorize its subdomains or third-party services.
• Your account-specific DNS TXT challenge or an HTTPS file under /.well-known/. Keep the challenge in place through testing; documents cannot replace this check.
• The UTC testing start and end dates, emergency contact, exclusions and any special rate or safety constraints.
• Credentials only through the approved secure handoff; never put passwords in checkout notes.

What happens after payment

Payment is available only after live domain-control verification succeeds for every exact hostname. A paid order is queued for a separate operator start within the chosen testing window. Domain control is checked again at start; missing or unavailable proof blocks testing. A paid order may be cancelled and refunded if control is lost or the scope is unsafe or unsupported.

Stop conditions

Testing may be paused immediately for an emergency request, instability, an unexpected third-party system, evidence of unauthorized scope, or a legal or safety concern. Use the emergency contact or email support@fabereye.com.