Libraries tagged by domain names

A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)

Go to Download

Checks spam lists by domain name and IP address

Go to Download

A bundle with a validator to exclude mails of mails domain names.

Go to Download

Check a domain name extension and adress using PSL

Go to Download

This template will attempt to verify the domain name where service will be rendered.

Go to Download

A simple PHP library that allows you to get all DNS records for a specified domain name.

Go to Download

Laravel Package for grabbing specific information about a domain name.

Go to Download

This test standalone Laravel library allows to get all DNS records for the specified domain name.

Go to Download

This library gets all DNS records for the specified domain name.

Go to Download

create short URL with your own domain name

Go to Download

Domain Parser, parses and validates a domain name.

Go to Download

A library for encoding and decoding internationalized domain names.

Go to Download

Name.com Domain Registrar API Client

Go to Download

A lightweight PHP package that provides country data with powerful lookup functionality. Easily retrieve country details by name, code, domain extension, calling code, currency, and capital, all from a single source of truth.

Go to Download

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