Works with the AI Agents you already use
CDN Edge Probe
Partial reachability — where a site loads but a login button, captcha, or asset subdomain fails — is usually written off as "the network is flaky".
Free
CDN Edge Probe
Example session with this skill installed
A specific subdomain for my site is timing out, but the main page works. Can you diagnose if it's an IP block and find a working edge node?
- Read your context and instructions
- Compiled the cdn edge probe
I analysed the connectivity for the target subdomain. The initial DNS resolution pointed to a blocked IP range, but I successfully identified a reachable edge node via TLS probing.
Connectivity Diagnosis
DNS resolution
api.target.exampleresolved to 2 addresses, both in a range where all three TCP handshakes timed out
Three-state TLS probe
| IP | Real SNI | No SNI | Forged SNI | Verdict |
|---|---|---|---|---|
| 203.0.113.45 | TCP_TIMEOUT | TCP_TIMEOUT | TCP_TIMEOUT | IP-range blocked |
| 203.0.113.46 | TCP_TIMEOUT | TCP_TIMEOUT | TCP_TIMEOUT | IP-range blocked |
Nothing answered a handshake, which rules out SNI-level filtering: a filtered host still completes TCP and fails at TLS.
Edge scan
Sampled 90 IPs from the CDN's published ranges and found 6 that complete a handshake, 2 of which also served real content:
198.51.100.24 HTTP 200 size=580312
198.51.100.61 HTTP 200 size=579844
What to do next
Pin the fastest one in your hosts file. The command needs administrator privileges, and writes are wrapped in START/END markers so --revert undoes exactly this block:
python scripts/fix_hosts.py --set 198.51.100.24:api.target.example
Two caveats worth knowing before you rely on this:
- Preferred IPs expire. CDN node health changes; an IP working today may fail in a few weeks and needs rescanning.
Do not hammer the probe. One batch of several dozen IPs is enough to get your egress throttled and manufacture a false "IP-range blocked" verdict. Space rounds 30 seconds apart.
Connects securely to your tools. The creator never sees your data.
About this skill
Partial reachability — where a site loads but a login button, captcha, or asset subdomain fails — is usually written off as "the network is flaky". It is not. There are exactly four causes, and each has a different fix. This skill identifies which one you are looking at before suggesting anything.
The four causes
| Real SNI | No SNI / forged SNI | Diagnosis | Does changing IP help |
|---|---|---|---|
| succeeds | — | Reachable | — |
| fails | succeeds | SNI-level filtering | Briefly only |
| fails | fails | IP-range blocking | Yes — switch edge IP |
| resolves into an unrelated netblock | — | DNS poisoning | No real IP to work with |
Almost every guide answers this class of bug with "change your hosts file" or "switch DNS". For two of those four rows, neither can possibly work.
What it does
- Three-state TLS probing runs each candidate IP through three handshakes — real SNI, absent SNI, and forged SNI — and reports a verdict per IP. This is what separates "the domain is being filtered" from "this IP range is dead".
- CDN edge scanning samples a provider's published ranges for nodes that complete a handshake, with an optional real HTTP GET to confirm the node actually serves content rather than just completing TLS.
- Targeted hosts patching writes the chosen IP inside START/END markers, so rollback removes exactly this tool's block and never touches entries written by other software. A timestamped backup is written before every change.
What you get
- scripts/probe_tls.py
- scripts/scan_ips.py
- scripts/fix_hosts.py
- SKILL.md, README.md
Python 3.8+, standard library only, no pip install.
Honest limits
- Only useful for multi-edge CDNs (CloudFront, Akamai, Fastly, Cloudflare). Single-origin sites have no alternate edge to switch to.
- Useless against whole-range blocking and DNS poisoning. Those need the real IP first, obtained by other means.
- Not a proxy. It changes which edge node you connect to, never your egress.
- Preferred IPs expire. A working IP can stop working in weeks and must be rescanned.
- Probing is itself a disturbance. One batch of several dozen IPs, or several rounds of timing runs, can get your egress throttled — turning working IPs into failing ones and manufacturing a false "IP-range blocked" verdict. Pace it: 30 seconds between rounds, 30 targets per round.
Permissions
One script modifies the system hosts file and therefore needs administrator or root privileges. The other two open outbound TCP/443 connections to candidate IPs. Both are documented in the Permissions section of SKILL.md.
No telemetry, no analytics, nothing leaves your machine. The only environment variable read is SystemRoot, used to locate the hosts file on Windows.
MIT licensed. Read the scripts before you run them — they are short.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.
Requires root/admin privileges for hosts file modification. Excessive scanning may trigger temporary egress rate-limiting. SNI forgery may produce false negatives on CloudFront.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed today
- Free with an Agensi account
- Accounts
Target
- Software
Python
Git
Permissions
Allowed Hosts
File Scopes
Terminal and Read: runs the three bundled Python scripts. Write: fix_hosts.py modifies the system hosts file, which is why administrator privileges are required for that one step. Network Access: the TLS probes and edge scans open outbound TCP/443 connections to the candidate IPs. File scopes are limited to scripts/** because nothing outside the skill directory is touched, apart from the hosts file itself.