Managed challenge
Human confirmation flow
The visitor receives a controlled challenge page and the edge verifies a signed action before issuing clearance.
DNS-routed edge protection
Put your site behind a pulsar-class edge shield.
PulsarCDN combines authoritative DNS, live edge routing, origin proxying, in-memory cache, request middleware, bot challenges, and traffic visibility in one control plane.
DNS
authoritative routing
L7
HTTP/S proxy
Bot
challenge gate
Logs
edge visibility
Active zone
edge online
example.com → ns1.pulsarcdn.com / ns2.pulsarcdn.com
Before origin
Filter
Block bad IP ranges, paths, headers, query patterns, and user agents before they reach your server.
Traffic control
Challenge
Use managed, JavaScript-assisted, proof, math, image, or simple checks with signed clearance.
Request path
01DNS sends the visitor toward a healthy PulsarCDN edge.
02Middleware rules decide whether to allow, block, rate-limit, or challenge.
03Clean traffic is proxied to origin or served from edge cache when available.
04Metrics and request logs return to the dashboard for domain-level visibility.
Network model
DNS, edge routing, and origin shielding in one loop.
When a domain uses PulsarCDN nameservers, zone data is synced to edge nodes. Proxied records resolve to the edge network, while DNS-only records remain normal DNS answers.
The control plane keeps track of edge health, public edge IPs, domain metrics, middleware logs, origin cache settings, and certificate availability.
Visitor
browser request
Pulsar Edge
filter + cache + proxy
Origin
your app server
Health
Central checks edge availability and excludes nodes that should not receive proxied traffic.
Certificates
Edge nodes fetch and cache TLS certificates for proxied hostnames.
Cache
Eligible origin responses can be cached at the edge to reduce repeated origin load.
Protection stack
Challenge suspicious traffic without sending it straight to origin.
PulsarCDN checks requests at the edge first. You can combine rules, rate limits, and challenge modes so normal visitors continue while noisy or suspicious traffic is slowed down.
Browser proof
Edge-issued token checks
Proof challenges rely on edge-bound tokens, timing windows, request headers, and replay protection instead of trusting client-side JavaScript alone.
Visual or math
Interactive verification
Use image and math challenges when you want visitors to solve a clear task before traffic is allowed forward.
Rate limits
Slow down bursts
Set request windows for a domain and choose whether rate-limited visitors should see a challenge or an error response.
Rules
Block unwanted patterns
Block by IP/CIDR, path, user agent, headers, and query strings before proxying to your application.
Clearance
Let clean visitors continue
After a challenge is solved, a signed clearance cookie lets the same visitor continue through the edge without repeating checks immediately.
Operator workflow
Everything is configured from the dashboard.
01
Add domain
Add a zone, point it at PulsarCDN nameservers, and watch propagation status from the panel.
02
Create records
Choose DNS-only records or proxied A records that route visitors through the edge network.
03
Enable edge controls
Turn on middleware, challenge modes, origin cache, and request logging per domain.
04
Monitor traffic
View edge nodes, domain RPS, counters, recent requests, and blocked/challenged traffic.
Ready for launch
Start routing a domain through PulsarCDN.
Create a zone, add your records, choose the protection mode you want, and let the edge network handle the first line of traffic.