iptocc
Python bindings for the iptocc Rust crate. Offline IPv4 and IPv6 to ISO 3166-1 alpha-2 country code lookup.
Note: Country codes reflect the country assigned by a Regional Internet Registry (RIR) to each IP block, not where the block is being used. RIR data agrees with MaxMind for ~95% of IPv4 addresses and has minimal discrepancies for IPv6 (Zander, 2012).
Important: iptocc 3.0 is a complete Rust rewrite. Versions 2.x and earlier were pure Python on top of pandas. The public API stays mostly compatible (see migration notes below), single-lookup latency dropped from ~78 ms to ~44-141 ns, and a batch API was added.
Features
- Offline lookup, no API keys, no network calls
- IPv4 and IPv6 in one call
- Single string OR batch (any iterable of strings)
- Lookup data embedded in the wheel; no runtime file I/O
iptoccCLI installed withpip install iptocc- Data refreshed nightly from the five Regional Internet Registries
Install
Requires Python 3.10 or newer.
pip install iptocc
Usage
from iptocc import country_code
country_code("8.8.8.8") # "US"
country_code(["8.8.8.8", "1.0.16.1"]) # ["US", "JP"]
A CLI is installed alongside the library:
$ iptocc 8.8.8.8 1.0.16.1
8.8.8.8 US
1.0.16.1 JP
Migrating from 2.x
# 2.x
from iptocc import get_country_code, CountryCodeNotFound
try:
cc = get_country_code("8.8.8.8")
except CountryCodeNotFound:
cc = None
# 3.x
from iptocc import country_code
cc = country_code("8.8.8.8") # returns None on miss
See also
- iptocc — the Rust crate this binding is built on
- @roniemartinez/iptocc — WASM/JavaScript bindings
- GitHub repo
2 maintainers
Metadata
2 maintainers
Release files for iptocc 3.3.171
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iptocc-3.3.171.tar.gz | 449.0 kB | With provenance | Details for iptocc-3.3.171.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| iptocc-3.3.171-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details for iptocc-3.3.171-cp310-abi3-win_amd64.whl |
| iptocc-3.3.171-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ x86-64 | Details for iptocc-3.3.171-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| iptocc-3.3.171-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ ARM64 | Details for iptocc-3.3.171-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
| iptocc-3.3.171-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details for iptocc-3.3.171-cp310-abi3-macosx_11_0_arm64.whl |
| iptocc-3.3.171-cp310-abi3-macosx_10_12_x86_64.whl | CPython 3.10 | abi3 | macOS 10.12+ x86-64 | Details for iptocc-3.3.171-cp310-abi3-macosx_10_12_x86_64.whl |
Total release size: 3.5 MB
Release files / iptocc-3.3.171.tar.gz
| Download URL | iptocc-3.3.171.tar.gz |
|---|---|
| Size | 449.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ae8ae57326bbe971b012600582fb2a1abc6dbff1bc7aec5ebfd37765ca2595a
|
|
BLAKE2b-256 checksum How to use checksums |
3091f973587657c6bb79d37263b0151e0a13fa0cd081b8dd3336fed2f11f29f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / iptocc-3.3.171-cp310-abi3-win_amd64.whl
| Download URL | iptocc-3.3.171-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 523.4 kB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
76a12db8029317e2d72000872059d31be51d816517d8038e03da44ebf250f503
|
|
BLAKE2b-256 checksum How to use checksums |
e6c8bc9967e98a2a1b71375dd7f4e0f6af252046cb0121a119f03ca967fd608a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / iptocc-3.3.171-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | iptocc-3.3.171-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 628.4 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
cd53a9ed808391e73c4a47d318a56188b31450a5c87968a2230c98bcee4fa67c
|
|
BLAKE2b-256 checksum How to use checksums |
216b4afbfbfc18a56d02baab2a803641d3a5c829c0b4bbebada8aad75aee6813
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / iptocc-3.3.171-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | iptocc-3.3.171-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 628.6 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
bd0d802bddb09047e703286ab82a89528e141210fccd348ce11d6388209875a1
|
|
BLAKE2b-256 checksum How to use checksums |
8027d0ba181a65c6ac8012e64b25dc57b8a78e4982da59a86520c3209f018766
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / iptocc-3.3.171-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | iptocc-3.3.171-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 621.9 kB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c79e9d8cbdf815cb0c5004db22e192b5b6ab3784a1d5ed3331b95917e6951f84
|
|
BLAKE2b-256 checksum How to use checksums |
fa45a442d1225e461e7793ba36acacd5357cd099e3407cac0a02a31d26eb922b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / iptocc-3.3.171-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | iptocc-3.3.171-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 622.1 kB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
7e7c11b7575cfd84f78c9dedff4cb1e87c7c52b5fb63bc5d6e7d06cbfb78314f
|
|
BLAKE2b-256 checksum How to use checksums |
a5772a2fa7bcfe4f3d2ee8fc02c9df766c5c860f26ee0de561d192bbd50002fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logSecurity for iptocc 3.3.171
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 6 files in this release have been uploaded with provenance metadata.
Attestation for iptocc-3.3.171.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
