Network access
Unblock apsera.ai on your corporate network
If a Fortinet, Cisco, Palo Alto, Symantec, Zscaler, or Forcepoint web filter is blocking apsera.ai, it’s almost certainly because the domain is new and the classifier hasn’t rated it yet. This page is what you can forward to your IT/security team so they can verify us and allow the domain in under five minutes.
Need to get in right now? Use the alternate URL.
The exact same application is served at https://apsera-portal.onrender.com. It runs on Render (a US-based hosting provider classified globally as Technology), so corporate web filters typically allow it through even when apsera.aiis still being rated. Sign in there with the same credentials. Your data, billing, and workers are identical — the URL is the only difference.
Who we are
Why the filter blocked us
Enterprise web filters (Fortinet FortiGuard, Cisco Talos / Umbrella, Palo Alto URL Filtering, Symantec Bluecoat, Webroot BrightCloud, Zscaler, Forcepoint) maintain category databases for every known domain. New domains land in a default-block bucket — usually called Not Rated or Newly Registered Domain— until they’re classified.
apsera.ai is a recently launched B2B SaaS, so until each classifier’s database catches up, networks with strict default-block policies will block us. We’ve submitted apsera.ai to the major classifiers for re-categorization as Business / Information Technology — propagation usually takes 24 to 72 hours.
For your IT / security team — copy + paste
Forward the block to your network admin with this message. We’ve found this wording gets approved within an hour at most enterprises.
Hi IT/Security, Could you please add an allow-list entry for apsera.ai (and *.apsera.ai) on our web filter / proxy? Vendor: apsera.ai — B2B AI workforce SaaS Legal entity: APBLD APP BUILD LLP, registered in India Domain: apsera.ai (canonical: https://www.apsera.ai) Suggested category: Business / Information Technology / SaaS Compliance + diligence pages: https://www.apsera.ai/trust (data residency, encryption, deletion) https://www.apsera.ai/privacy https://www.apsera.ai/terms https://www.apsera.ai/dpa https://www.apsera.ai/.well-known/security.txt The vendor has already submitted the domain for re-categorization at Fortinet, Cisco Talos, Palo Alto, Symantec Bluecoat, Forcepoint, Zscaler, and Webroot — but our filter's local database may not have refreshed yet. A manual allow entry will unblock me until that propagates. Thanks, [your name]
Per-vendor allow-list paths
If your team needs the exact place to add the entry, here are the most common ones.
Verifying we’re legitimate before allowing
Your security team can independently verify every claim on this page:
- TLS cert — visit ssllabs.com/ssltest/analyze.html?d=www.apsera.ai for Qualys SSL Labs report.
- WHOIS — registrar + creation date are public: lookup.icann.org/en/lookup?q=apsera.ai
- security.txt — RFC 9116 contact for security reports: /.well-known/security.txt
- Hosting — all production traffic terminates at Render (a US-based hosting provider operating since 2019). Reverse-DNS will resolve to a Render-owned hostname.
Still need help?
Email [email protected] and we’ll respond within one business day with whatever diligence material your security team needs (SOC-equivalent statement, data flow diagram, sub-processor list).