Overview
Organizations that use managed networks, firewalls, or other security software may need to allowlist Certiverse destinations so candidates can launch and complete exams without interruption. This article lists the domains and URL schemes used during exam delivery and outlines how to configure and validate allowlist rules.
Share this article with the network or security team responsible for your environment, and complete the configuration before candidates begin testing.
Recommended Allowlisting Approach
Allowlist by domain rather than by individual URL. Exam URLs are dynamic and can vary by exam ID, path, query string, or delivery session. Domain-level rules reduce the risk of valid exam traffic being blocked when a full URL changes.
Required Destinations
The table below lists the domains and URL schemes that must be reachable from candidate devices during exam delivery.
| Domain or URL Scheme | Purpose | Required Action |
| certiverse.com | Primary Certiverse domain used throughout the candidate experience | Allowlist the domain |
| signalr-processor.azurewebsites.net | Used during exam delivery | Allowlist the domain |
| pvalue.blob.core.windows.net | Used during exam delivery and for Safe Exam Browser (SEB) launch resources | Allowlist the domain |
| sebs://https://pvalue.blob.core.windows.net | URL scheme prefix used for Safe Exam Browser (SEB) commands | Ensure security software does not block this scheme or prefix |
Allowlist Configuration and Validation
- Add the listed domains to all applicable firewall, proxy, DNS filtering, secure web gateway, and endpoint allowlists
- Configure rules at the domain level where possible, rather than pinning a single path or query string
- Confirm that Safe Exam Browser commands using the sebs:// scheme are permitted
- Validate the configuration from the same managed network and device profile that candidates will use
Additional Considerations
Full-URL Rules
Candidate launch URLs vary by exam, session, and environment. Allowlist rules tied to a specific full URL may block valid exam traffic and are not recommended.
Non-Production Environments
If you are testing in a QA or other non-production environment, confirm the applicable destinations with your Certiverse contact before testing.
Strict URL-Level Controls
Organizations that validate backend URLs individually or enforce strict URL-by-URL controls should coordinate with Certiverse before testing so any additional backend destinations can be provided.
Contact Us
If you have any questions or need additional assistance, please contact us by either emailing support@certiverse.com or by submitting a ticket from this article.
Updated
Comments
0 comments
Article is closed for comments.