Libraries tagged by email domain
ivolo/disposable-email-domains
39309 Downloads
disposable domains list
erag/laravel-disposable-email
21866 Downloads
A Laravel package to detect and block disposable email addresses.
mika56/spfcheck
935433 Downloads
Checks an IP address against a domain's SPF record
arubacao/tld-checker
1350225 Downloads
Top Level Domain (TLD) validation library for PHP
alariva/laravel-email-domain-blacklist
179743 Downloads
A Laravel package for adding email domain blacklist validation rule
nojacko/email-data-disposable
386614 Downloads
Disposable email domains
salaros/is-biz-mail
432483 Downloads
isBizMail tells you whether a given email address is free (gmail.com, yahoo.es, yandex.ru etc) or not
madeitbelgium/laravel-email-domain-validation
61338 Downloads
PHP Laravel Email domain validator
mdwheele/swotphp
45826 Downloads
Identify email addresses or domains names that belong to colleges or universities.
veeqtoh/laravel-active-email
475 Downloads
A Laravel package providing validation rule against disposable email addresses.
maize-tech/laravel-email-domain-rule
1710 Downloads
Laravel Email Domain Rule
mischasigtermans/laravel-sift
1305 Downloads
Extract and filter common email domains in Laravel.
pimlie/authres_status
2951 Downloads
This authres_status plugin checks the Authentication-Results headers of your emails and displays the verification status. The verification status is displayed when you read an email, but you can also add a column to your message list.
paypaplane/svix-client
16326 Downloads
Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.
insign/dumb-emails-validator
603 Downloads
Laravel validator for common email domain typos