Routing without anycast
DNS answers follow real-user latency and edge health.
CDN & EdgeGA
Faster sites, from the nearest edge
Add a domain, give each record a destination and you are done. Cache, SSL, WAF and smart routing are automatic — and Iranian and international visitors can be served by different edges.
- No anycast
- smart routing
- Free
- automatic SSL
- IR / intl
- traffic split
Geo routingLIVE
| Edge | Area | Status |
|---|---|---|
| thr-a | Iran only | online |
| thr-b | All | online |
| fra-1 | All except Iran | online |
| ist-1 | TR · AE · IQ | draining |
Live
HOW IT WORKS
How it works
- 1
Add a domain
Enter the domain; ownership is automatic when its DNS is on whycloud.
- 2
Records and destinations
Give each name your server IP or address.
- 3
Connect DNS
Set the CNAME or name servers shown on the page.
- 4
Security and cache
SSL is automatic; tune WAF, firewall and cache rules when needed.
Capabilities
CDN & Edge
Iran / international split
Each edge serves only Iran, everyone except Iran, or chosen countries.
Automatic SSL
Free certificates for every name, HSTS and minimum TLS.
WAF and rate limits
SQLi, XSS and traversal detection, IP/country firewall, rate limiting.
Connector
Private origins without public IPs or inbound ports.
Detailed reports
Requests, bandwidth, cache ratio, visitor country and ISP.
USE CASES
Use cases
Sites and stores
Fast loading everywhere while hiding the origin IP.
Video and large files
Deliver media and packages without loading the origin.
Attack protection
Under-attack mode, WAF, rate limits and country firewall.
Private servers
Publish services behind NAT with a connector, no open ports.
Technical specs
- Protocols
- HTTP/1.1 · HTTP/2 · WebSocket
- SSL
- Automatic ACME, wildcard with whycloud DNS
- Routing
- DNS steering + geographic areas
- Country reports
- ip66 database, refreshed daily
- Error pages
- Branded whycloud 4xx/5xx pages
RECORDS & DESTINATIONS
Write a record, give it a destination
No separate origin objects: give @, www or api an IP, IP:port or https:// address; several servers separated by commas balance load.
- Inline editing and CNAME hints
- Multiple destinations with health checks
- One-click cache purge
GEO ROUTING
In-country edges for Iran, global edges for the world
Network admins set a service area per edge. It applies to CDN steering DNS and to apex records on public DNS; if every edge of an area is down, traffic fails over to healthy edges.
- Iran / international split
- Advanced ASN rules
- Visitor IP simulator
FAQ
Frequently asked questions
Does whycloud CDN need anycast?
No. DNS answers are chosen from measured real-user latency to each edge and edge health.
Can Iranian traffic be served from an in-country edge and the rest from abroad?
Yes. Each edge gets a service area: Iran only, everyone except Iran, or a list of countries.
What do CDN error pages look like?
When your origin is unreachable or a request is blocked, visitors see a branded whycloud page with a request Ray ID and automatic retry.
How is it billed?
Delivered traffic per GB and requests per million; blocked requests are free.
Turn on your own cloud today
Create an account and connect your first server in under five minutes.