Fair Usage Policies

1. Intended use

Use PacketPint to verify your own connection, investigate a public host you are authorised to test, inspect a domain’s public DNS or registration data, or understand the information your browser and network expose. Typical use is a small number of manual checks while troubleshooting, validating a configuration or confirming a result.

2. Fair limits apply to every service

Every PacketPint service is subject to fair-use limits, whether or not a number is displayed on its page. Limits may apply per visitor, IP address, target, domain, session or time period. They can change when needed to protect service availability, third parties and the underlying infrastructure.

Please do not send oversized requests, unusually long input, excessive request bodies or automated batches to any service. Do not repeatedly query tools for many different hosts, domains, records, IP addresses or other information in a way that exceeds normal interactive use. The MX RBL Check applies both a visitor-hourly and domain-daily limit because each check can query external real-time blocklist operators. SMTP Server Check is limited per visitor and target server, connects only to port 25 and never sends a message body.

3. Prohibited activity

• Automating, scraping, polling or bulk-submitting requests without prior permission.
• Using PacketPint for scanning, enumeration, surveillance, load testing or denial-of-service activity.
• Testing systems, destinations or data that you are not authorised to access.
• Attempting to bypass rate limits, request validation, session controls or other safeguards.
• Submitting malicious, deceptive, unlawful, abusive or privacy-invasive content.
• Sending payloads that are unnecessarily large, malformed or intended to consume disproportionate resources.

4. Protecting destinations and data

Some tools cause a request to be made from PacketPint’s infrastructure. Results describe conditions observed from our server and may differ from your own network. Use the smallest practical number of checks and allow time between repeated tests. Public technical information can be incomplete or outdated; do not rely on it as the sole basis for security, operational or legal decisions.

5. Enforcement

We may delay, limit, reject or block requests and preserve minimal operational records needed to investigate abuse or protect the service. We may adjust or remove functionality without notice where this is necessary for reliability or security. Circumventing these measures is not permitted.

6. Community pages

Guestbook and Contact submissions must be short, relevant and respectful. Do not include passwords, credentials, sensitive personal data, spam, advertising or content you do not have the right to share. Contact messages are stored so they can be reviewed; Guestbook messages are publicly visible after submission.

7. Questions

If a legitimate diagnostic need requires more than normal interactive use, please use the Contact form before proceeding.