535 Unknown Application
The HTTP 535 Unknown Application status code is an
unofficial server error specific to Edgio (formerly
Layer0). The Edgio platform returns this code when the
incoming request's Host header does not match any
deployed project, preventing Edgio from identifying
which project to route the request to.
Usage
Edgio routes incoming requests to the correct project
based on the Host header. Each project registers
one or more hostnames (custom domains or
*.layer0-limelight.link / *.edgio.link subdomains)
during deployment. When a request arrives at an Edgio
POP with a Host value not matching any
registered hostname, the platform has no target
project and returns a 535.
Common causes include:
- DNS records (CNAME or A) point to Edgio IP addresses, but the corresponding hostname was never added to an Edgio project.
- The project was deleted or redeployed under a different hostname without updating DNS.
- A load balancer or upstream proxy rewrites the
Hostheader to a value Edgio does not recognize. - The request targets an IP address directly instead of a registered domain name.
Note
After migrating between Edgio platform versions (e.g., v6 to v7), previously registered hostnames need to be reconfigured in the new project. Stale DNS records pointing to old Edgio endpoints trigger 535 errors until the hostname mapping is updated.
SEO impact
Search engines treat Edgio 535 responses as server errors. Persistent hostname resolution failures reduce crawl rate and prevent indexing of affected URLs. Registering the correct hostname restores normal crawling.
Example
A client sends a request to an Edgio POP, but the
Host header does not match any known project. Edgio
returns a 535 error.
Request
GET / HTTP/1.1
Host: unknown.example.re
Accept: text/html
Response
HTTP/1.1 535 Unknown Application
Date: Mon, 02 Mar 2026 14:30:00 GMT
Content-Type: text/html
Server: ECAcc (dce/26A1)
<html>
<head><title>535 Unknown Application</title></head>
<body>
<h1>535 Unknown Application</h1>
<p>No project matches the requested hostname</p>
</body>
</html>
How to fix
Verify the Host header in the failing request
matches a hostname registered in the Edgio project.
Open the Edgio console, navigate to the project's
environment settings, and confirm the domain is listed
under custom domains or hostnames.
Check DNS records for the domain. The CNAME or A
record must point to the Edgio-assigned endpoint for
the specific project environment. Running
dig example.re confirms where DNS currently
resolves.
If the project was recently migrated to a new Edgio platform version, re-add all custom domains in the new project's configuration. Platform version upgrades do not automatically carry over hostname registrations.
Inspect any intermediate proxies, load balancers, or
CDNs sitting in front of Edgio. Confirm they forward
the original Host header unmodified. A proxy
rewriting the Host to its own internal hostname
causes Edgio to reject the request with a 535.
Takeaway
The 535 Unknown Application is an Edgio-specific
status code returned when the Host header in the
request does not match any registered project
hostname, typically caused by DNS misconfiguration or
missing hostname registration in the Edgio project
settings.