Libraries tagged by ip find

ayesh/geo-ip-database

8 Favers
388 Downloads

Weekly updated database of IP CIDR to Country codes, indexed by the first 1/4th of the IP address

Go to Download


yakeing/dnspod_api

6 Favers
55 Downloads

The DNSPod User API is restricted to individual users, making it easier and more flexible for users to manage their own domain names and records.

Go to Download


nazar-pc/upf

23 Favers
24 Downloads

Useful PHP Functions: set of system-independent functions from CleverStyle CMS

Go to Download


mindpowered/iptools

0 Favers
1586 Downloads

Tools for working with IP4/IP6 IP Addresses including IPv4, IPv6, CIDR, and Subnet Masks

Go to Download


labor-digital/max-mind-helpers

0 Favers
36 Downloads

Helper package to implement IP to geolocation resolving based on the MaxMind database

Go to Download


iicgo/circe

0 Favers
2 Downloads

IP address index to district in China

Go to Download


nael_d/guardify

0 Favers
0 Downloads

Robust CSRF protection for PHP applications with HMAC validation, IP/UA binding, and AJAX support.

Go to Download


lyhiving/dnspod_api

0 Favers
10 Downloads

The DNSPod User API is restricted to individual users, making it easier and more flexible for users to manage their own domain names and records.

Go to Download


lindelius/php-checkip

1 Favers
4 Downloads

A minimal, PSR based library for checking the public IP of the host machine.

Go to Download


minde/salto-ship

0 Favers
2 Downloads

A PHP Salto client implementing the PMS Industry Standard protocol via TCP/IP

Go to Download


rohsyl/salto

0 Favers
4124 Downloads

A PHP Salto client implementing the PMS Industry Standard protocol via TCP/IP.

Go to Download


kiwicom/loopbind

1 Favers
17 Downloads

🛠️️ CLI tool to easily bind localhost network interface with additional IP and ensure matching record in /etc/hosts.

Go to Download


coucounco/salto

1 Favers
1443 Downloads

A PHP Salto client implementing the PMS Industry Standard protocol via TCP/IP.

Go to Download


trukes/php-rate-limiter

2 Favers
1 Downloads

A lightweight, flexible rate-limiting library for PHP. Manage access limits by user, IP, or custom keys with support for sliding and fixed windows. Compatible with Redis, MySQL, and file-based storage. Ideal for controlling API usage and preventing abuse.

Go to Download


piurafunk/docker-php

0 Favers
8 Downloads

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download


<< Previous Next >>