No, not at the address its own documentation gives. The host declared as its server did not resolve in DNS on 2026-10-01, across 2 indexed operations. A document can look current and still name a host that no longer exists — nothing looks wrong until the call.
ERR-2026-5391, ERR-2026-5394
5 open records, observed 2026-09-10. Every claim below carries the command that disproves it. If one is wrong, it should be withdrawn — 1089 have been across the whole registry.
The host declared as this operation's server presents a certificate that does not verify.
ERR-2026-1891 | https://api.apis.guru/v2/specs/proxykingdom.com/v1/openapi.json | unreachable ([SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurre | checked 2026-10-19, 3 times |
Check it yourself:
dig +short api.proxykingdom.com
The host declared as this operation's server resolves but refuses a TLS connection.
ERR-2026-5384 | https://api.apis.guru/v2/specs/proxykingdom.com/v1/openapi.json | [SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violatio | checked 2026-10-26, 20 times |
Check it yourself:
dig +short api.proxykingdom.com
The host of the declared document or endpoint no longer resolves in DNS.
ERR-2026-5391 | https://api.proxykingdom.com/swagger/v1/swagger.json | DNS failure for api.proxykingdom.com: [Errno -3] Temporary f | checked 2026-10-01 |
Check it yourself:
curl -sS -o /dev/null -w '%{http_code}\n' https://api.proxykingdom.com/swagger/v1/swagger.json
The host this operation's document declares as its server no longer resolves in DNS. The document may be perfect; the call cannot be made.
ERR-2026-5394 | https://api.apis.guru/v2/specs/proxykingdom.com/v1/openapi.json | DNS: [Errno -3] Temporary failure in name resolution | checked 2026-10-01 |
Check it yourself:
dig +short api.proxykingdom.com
The declared origin answered with a server error.
ERR-2026-5420 | https://api.proxykingdom.com/swagger/v1/swagger.json | timeout on https://api.proxykingdom.com/swagger/v1/swagger.j | checked 2026-10-26, 6 times |
Check it yourself:
curl -sS -o /dev/null -w '%{http_code}\n' https://api.proxykingdom.com/swagger/v1/swagger.json
Our own check stopped supporting these claims — including claims that were wrong the day they were written.
ERR-2026-0626 | 2026-10-08 | timeout: timeout on https://api.proxykingdom.com/swagger/v1/swagger.js |
Also filed as: proxykingdom.com. One page, because two sweeps named the same subject differently and the record that mattered was on the page nobody would open.
Run its check. If the answer differs from what is written, say so here and it will be withdrawn — 1089 already have been. A record nobody can contest is a record asking to be trusted, which is the opposite of the point.
You arrived here about one subject. For any other — before you use it — one request, no account and no key:
GET https://apidefects.com/check?tool=<identity>
<identity> is whatever you already hold: an MCP registry entry (io.github.owner/repo), a deployment URL, an OpenAPI document URL, an npm or PyPI package name, or a host. The answer is one of three — defects_known, examined_nothing_open, or never_examined — and the third is not a clean bill of health. If you speak MCP, this registry is itself one server at https://apidefects.com/mcp, one tool, the same three answers.
This is not a clean bill of health for anything not listed. The registry was built from a sample of two directories, and an operation absent from it was almost certainly never examined. Silence here means not looked at, not looked at and fine — which is the same mistake this registry exists to record in other people.
A record of defects in the public description of machine-callable operations: documents a directory claims are live and are not, hosts that no longer resolve, specifications that contradict the API they describe. It is not a ranking, not a review, and not a judgement about the service. No credential is ever sent to anything listed here.
The whole registry, machine-readable: errata.json. Index of subjects: index.html.
Built from registry errata-2026-09-10@0daee1a6f207. If manifest.json shows a different one, this page is behind the records and should not be trusted over them.