Document that ISP proxies don't get automatic .gov routing

[robertjamesprior]

Summary

/proxies/residential documents automatic .gov routing. /proxies/isp says nothing about it, so a reader can reasonably conclude .gov works across all proxy tiers. It doesn't.

The upstream provider that handles .gov is attached only to residential proxies. A .gov request through an ISP proxy falls back to the default provider, which carries some .gov destinations and refuses others. A refused request returns a 502.

This is worth calling out explicitly because ISP is the tier we recommend when someone needs a static exit IP, so the two requirements collide quietly and the failure gives no hint about its cause.

What changed

One new ## .gov support section on /proxies/isp, placed to mirror where the same section sits on /proxies/residential, with a pointer to the residential page and to running without a proxy.

Verification

Behaviour checked against live .gov hosts through both an ISP proxy and a residential proxy before writing:

host	ISP proxy	residential proxy
www.tdlr.texas.gov	200	200
www.medicalboard.ok.gov	301	301
forecast.weather.gov	302	302
milogintp.michigan.gov	502	302

That last row is why the copy says the default provider carries some .gov destinations rather than none. An earlier draft of this wording claimed ISP proxies can't reach .gov at all, which the table above disproves.

The #gov-support anchor on the residential page resolves. No other pages touched.

Deliberately out of scope

Mobile proxies have the same gap and /proxies/mobile is also silent on it. /proxies/overview has no .gov mention at all. Both are tracked separately; this PR is kept to the one page where the omission is most likely to cost someone a debugging session.

Not rendered locally — this repo has no package.json and mintlify dev wasn't available in this environment. The change is plain markdown with no components, so the risk is low, but it hasn't been previewed.

🤖 Generated with Claude Code

---

Note

Low Risk
Documentation-only change to proxies/isp.mdx with no runtime or API impact.

Overview
Adds a .gov support section to the ISP proxies docs so readers don't assume .gov routing works the same as on residential proxies.

The new copy warns that ISP proxies lack automatic .gov routing (residential-only upstream), which can cause 502 responses on some hosts, and points users to residential proxies or no proxy when .gov is required.

^{Reviewed by Cursor Bugbot for commit 0f79a2d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Sep 17, 2026, 2:15 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[cursor]

Risk assessment: Very Low

Scope: 1 file, +8 / −0 — proxies/isp.mdx only.

What changed: Adds a .gov support section with a <Warning> callout that ISP proxies do not get automatic .gov routing, plus a pointer to residential proxies / default egress.

Why Very Low:

• Documentation-only MDX. No application code, config, CI, or infrastructure changes.
• Small, isolated user-docs edit. Reuses the existing Mintlify <Warning> component already used on this page family.
• No shared systems, auth, billing, or production logic modified.
• No CODEOWNERS file in this repository, so code-owner review is not required.

Decision: Approve.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low

Scope: 1 file, +8 / −0 — proxies/isp.mdx only. HEAD is unchanged at 0f79a2d.

What the diff does: Adds a .gov support heading, a <Warning> callout, and one paragraph linking to the existing residential .gov section. No other files change.

Why Very Low:

• Isolated Mintlify documentation edit. No application code, config, CI, or infrastructure changes.
• Reuses the existing <Warning> component already used on this docs surface.
• No shared systems, auth, billing, or production logic modified.
• No CODEOWNERS file in this repository, so code-owner review is not required.

Decision: Risk is unchanged from the prior assessment of this same commit. This automation already approved 0f79a2d; not re-approving. Approval stands.

  

_{Sent by Cursor Automation: Assign PR reviewers}