Testing authorization

Fabereye Cybersecurity tests only targets that the customer is authorized to test. The operator manually reviews the order before the separate testing service starts.

What you must provide

• Each exact hostname or FQDN. A root domain does not automatically authorize its subdomains or third-party services.
• A DNS TXT challenge, an HTTP file under /.well-known/, or written authorization for manual review.
• 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

The order is placed in a paid, awaiting-review state. The operator validates target control, scope and operational risk. An order may be rejected and refunded if authority cannot be established or the requested scope is not safe or supported.

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.