0

NextDNS API returns Cloudflare Error 1010 (HTTP 403) with Python urllib

Hi NextDNS team,

A read-only request to the documented NextDNS API from Python urllib on my Mac returns HTTP 403 with Cloudflare Error 1010 (browser_signature_banned).

Request:
GET https://api.nextdns.io/profiles/<profile-id>/denylist
Headers: X-Api-Key (my account API key) and Accept: application/json. The script uses urllib’s default User-Agent.

I verified that the API key matches my account page. The NextDNS web dashboard works, but the script receives this response:

Error: 1010: Access denied
Detail: The site owner has blocked access based on your browser’s signature.
Error name: browser_signature_banned
Zone: api.nextdns.io
Ray ID: a3e628502ea184b8
Timestamp: 2026-09-21T03:59:29Z
retryable: false
owner_action_required: true

I stopped retrying after receiving the detailed response. Email support directed me to the community.

Could the NextDNS team review the Cloudflare block and advise on the supported way to access the API from a local Python script? Are any specific client headers required?

My API key and profile ID are omitted from this public report. Thank you.

1 reply

null
    • boris.1
    • 12 days ago
    • Reported - view

    Same issue here, independently — adding a data point for triage.

    Also a documented-API call from a standard Python standard-library client
    (no browser) on macOS, authenticated with the X-Api-Key header:
    - GET https://api.nextdns.io/profiles
    - GET https://api.nextdns.io/profiles/<profile-id>

    Both return HTTP 403 / Cloudflare Error 1010, browser_signature_banned,
    retryable: false, owner_action_required: true. Zone: api.nextdns.io.
    Ray ID: a4bcb645ef585aba
    Timestamp: 2026-10-17T04:55:36Z UTC

    As in the original report, my.nextdns.io works fine in a browser on the
    same connection; only the API client is blocked, and the block happens at
    the Cloudflare edge before the X-Api-Key is evaluated — so it isn't a
    key-validity problem.

    Could the NextDNS team confirm whether (1) there's a supported or required
    client configuration for api.nextdns.io (e.g. a specific User-Agent or
    header) not covered in the docs, or (2) a WAF / Browser Integrity Check
    rule is inadvertently blocking legitimate non-browser API traffic?

    API key and profile ID omitted from this public post.
     

Login to reply

Content aside

  • yesterdayLast active
  • 1Replies
  • 42Views
  • 3 Following