Need help, found a bug, or want to discuss a partnership? This page explains the best ways to contact IPIN.IO. To keep things efficient and secure, please choose the category that matches your request and include the details we ask for.
Quick guidance: For general questions and collaborations, email business@ipin.io. If you’re reporting a security issue, please email the same address with “Security” in the subject and avoid sending sensitive secrets (passwords, private keys, full tokens).
1) Contact Channels
Email (preferred). You can reach the IPIN.IO team at business@ipin.io. Email is the fastest way for us to identify the request type, reproduce issues, and keep a clear record of what was discussed. We generally respond as soon as possible during normal working days.
Website links. You may also use the footer links (e.g., Privacy Policy, Terms of Use, Contact) to navigate to the relevant pages. If your request relates to a specific tool page, please include the exact URL so we can locate the correct feature quickly.
2) What to Include in Your Message (So We Can Fix It Fast)
Bug reports and tool issues. If something doesn’t work (blank results, errors, incorrect parsing, inconsistent output, slow response), please include: (a) the tool name and page URL, (b) what you expected to happen, (c) what actually happened, (d) your browser name/version and OS, and (e) the approximate time you tested it. Screenshots are helpful. If the issue involves a batch input, consider sending a minimal reproducible example (a small subset of the input) rather than the full dataset.
Data questions and accuracy disputes. If you believe an IP location or ASN output is incorrect, please include the target IP, the tool you used (single lookup, multi-platform comparison, batch lookup), and any reference result you are comparing against. Note that IP intelligence can vary across sources and can change over time, especially for CDNs, mobile networks, and shared hosting ranges.
Partnerships and business inquiries. If you want to discuss API access, dataset collaboration, advertising, or enterprise usage, please describe your use case, expected volume, countries/regions of interest, and any technical constraints (latency, output format, integration needs). The more context you provide, the faster we can assess fit and propose options.
3) Security & Privacy Notes
Please do not email secrets. Do not send passwords, private keys, full access tokens, authentication cookies, or sensitive account credentials. If your report requires demonstrating a problem involving authorization headers or tokens, redact them (e.g., keep only the first and last 3–4 characters) or replace them with placeholders.
Log files may contain sensitive information. If you are contacting us about the Log Analysis Tool and want to attach a snippet, please remove or mask sensitive fields such as Authorization headers, cookies, session IDs, user identifiers, or internal IPs that should not be shared. Share only the minimum excerpt needed to reproduce the issue.
Zero-retention design reminder. IPIN.IO is designed not to retain query inputs, uploaded logs, or query history. However, email is outside the query flow—anything you send via email is content you chose to share. Please keep messages minimal and redact sensitive data.
Contact: business@ipin.io · Operator: IPIN ChainLink Limited