92 free online tools for network diagnostics, IP lookup, email authentication, DNS records, privacy and leak testing, browser fingerprinting, SSL checking, and developer utilities. Every tool runs at the URL you visit — no software downloads, no account, no usage limits. Built for developers, sysadmins, security researchers, and privacy-conscious users.
Quick Answer: What Tools Does TrustMyIP Offer?
TrustMyIP provides 92 free online tools across nine categories: AI Crawler, Bot Verification & Crawl Rules (12), Email Authentication & Deliverability (13), DNS, Domain & Web Infrastructure (9), Network Diagnostics & IP Intelligence (17), IP Address Converters (14), Subnet, CIDR & Range Planning (5), Privacy & Leak Testing (12), Browser & System (4) and Developer Utilities (6). Every tool is free, runs in the browser, and needs no installation or account.
Twelve tools for one question: is that crawler in your logs really who it says, and what have you actually told it to do? Each verifier reads the operator’s own live published ranges rather than trusting the user-agent string, and each says so plainly when a check could not run rather than calling a real crawler fake. The last two read the files on your side of the exchange — robots.txt and llms.txt — and tell you what a crawler reading them would conclude.
Check any crawler address against 19 operators.
Which of Google’s five crawler categories.
Reverse DNS plus Microsoft’s published list.
Which of OpenAI’s four crawlers it is.
Anthropic’s one combined range list.
Where a non-match means three different things.
Verify 200 addresses in one pass.
Does the address back the claim?
Find fake crawlers in a whole log.
robots.txt and firewall rules from live ranges.
Which rule wins for a URL, and for which crawler.
Validate the proposed llms.txt file on any site.
Thirteen tools for the two questions mail raises: does your domain prove who it is, and will receivers accept it. The first eight read or write the five records that decide that — SPF, DKIM, DMARC, MTA-STS and BIMI. The rest work on a message that already exists, an address you are about to send to, and the reputation of the IP doing the sending.
SPF, DKIM, DMARC, MTA-STS and BIMI in one pass.
Record syntax, plus the ten-lookup limit counted.
Build a record that stays inside that limit.
Find the selector and read the published key.
Validate a DMARC record against RFC 9989.
Write a policy record, including the np tag.
DNS record, policy file and certificate together.
Logo record, SVG rules and VMC requirements.
Trace a message and check it for forgery.
Why a sending address gets mail refused.
Check one address against the major DNSBLs.
Syntax, MX, and mailbox check.
Detect disposable email addresses.
Nine tools for the layer between a name and a server. Look up records, watch a change spread across the world’s resolvers, walk a signed zone’s chain of trust, read the service records that clients actually follow, and check the certificate, headers and redirects a browser will meet when it arrives.
Nine record types, including PTR and CAA.
One record, asked of resolvers around the world.
Walk the chain of trust from the root down.
Service records for SIP, XMPP, LDAP and more.
Domain registration and ownership.
Certificate validity and trust chain.
HTTP request and response headers.
Trace redirect chains and status codes.
Which platform a site runs, and how it says so.
Seventeen tools that answer questions about a specific address: where it is registered, who announces it, whether it belongs to a cloud provider, a Tor relay or a proxy, and how the path to it behaves. Start with the address itself, then move outwards to the network that owns it.
Trace IP to city, ISP, and coordinates.
What the registry actually says about your address.
A full security and privacy readout for one address.
Run every IP check on one address in a single pass.
Find all domains on a server IP.
Check fraud risk and abuse probability.
Find which network owns an IP or domain.
Every CIDR block an AS announces, ready to export.
Detect AWS, GCP, or Azure IPs.
Check if an IP is a Tor relay node.
Detect proxy and VPN usage.
Measure latency to any server.
Scan for open ports and vulnerabilities.
Find maximum transmission unit size.
Measure download and upload bandwidth.
Identify hardware vendor from a MAC.
Random and locally administered MAC addresses.
An address is one number written many ways, and these fourteen tools move between them in both directions. Binary for the bits a mask operates on, decimal for the integer a database should store, hex and octal for the obfuscated links that turn up in phishing mail, and the IPv4–IPv6 forms that appear in logs when a dual-stack server writes down a v4 connection.
IPv4 as 32 bits, grouped by octet.
Read 32 bits back as a dotted address.
IPv4 or IPv6 to an integer, and back.
IPv4, IPv6, and decoding obfuscated links.
Octal form, and why leading zeros break parsers.
Expand a compressed IPv6 address to full form.
Shorten an address by the RFC 5952 rules.
All 128 bits, grouped as the address is written.
Mapped, compatible and 6to4 forms side by side.
Pull the embedded IPv4 address back out.
Pull every address out of a block of text.
Numeric order for IPv4, IPv6 and CIDR.
Generate random IPv4 and IPv6 addresses.
A phone number as an IP-shaped string, and back.
Five tools for the arithmetic behind firewall rules and addressing plans: turn a prefix into a range, a range into the smallest set of prefixes, and a list of prefixes into the shortest rule set that still covers the same addresses — then check which rule a given address actually matched.
Twelve tools that show what a site, a tracker or a swarm can already see. The first three test for leaks — what your browser, your WebRTC stack and your torrent client hand over without being asked. The rest measure the fingerprint itself: the signals that identify a device even after cookies are cleared.
Comprehensive browser leak audit.
Check if WebRTC leaks your real IP.
See the address your torrent client announces.
Detect your SSL/TLS client signature.
Detect GPU-based canvas tracking.
Analyze your audio processing signature.
See which fonts your browser exposes.
Check if the Battery API leaks data.
Do your browser signals contradict each other?
Detect timezone versus IP mismatches.
Check if referrer URLs are leaked.
Strip location metadata from photos.
Four tools that read what your own device reports: the browser’s own description of itself, the hardware behind it, the display in front of you, and the cookies already stored.
Six encoding, hashing and formatting utilities that run entirely in the page. Nothing you paste into them is sent anywhere, which is the point: they are safe to use on data you would not put into a web form.

Robert Harrison
OSINT & Network Utility Expert
Robert curates the TrustMyIP catalogue of 92 tools across AI crawler verification, network and IP diagnostics, email authentication, DNS, address arithmetic, privacy analysis and developer utilities. Each tool page names the source its answer came from.
View All ArticlesEvery time you connect to the internet, your device shares data with hundreds of servers — your IP address, browser fingerprint, hardware specs, screen resolution, installed fonts, and even battery level. Most people have no idea how much information leaks from their browser. That is exactly why free online tools matter.
These 92 network tools and privacy tools let you see exactly what a server, a tracker, a mail receiver or a crawler sees. Instead of installing desktop software or browser extensions — which add their own tracking — every tool runs at the URL you visit. Enter a domain or an address, click once, and read the result. Whether you are chasing a DNS change that has not taken effect, working out why a mail provider is refusing your messages, checking whether a VPN is actually hiding you, or auditing a certificate before launch, the right tool is one click away.
The catalogue is organised into nine categories rather than one long list, because the questions people arrive with fall into distinct groups. The jump links at the top of this page go straight to each one.
All 92 tools are free: no accounts, no subscriptions, no hidden limits. The developer utilities — Hash Generator, JSON Formatter, Base64 Encoder, URL Encoder and Password Generator — run entirely in the page, so what you paste into them is never sent anywhere.
A user-agent is a sentence a client writes about itself. Anyone can send Googlebot/2.1 from any machine on earth, and your access log will record it exactly as it records the real thing. That is why the verifiers in this category ignore the header entirely and test the two things a client cannot forge: the source address, and what the operator’s own nameservers and published range files say about it.
Each operator makes that harder in a different way, which is why there is a page per operator rather than one generic checker. Google publishes five separate range files and documents reverse DNS. Microsoft documents reverse DNS too, and its published list disagrees with it on at least one subnet. OpenAI publishes four files with overlapping prefixes and no reverse DNS at all. Anthropic publishes one combined file covering three crawlers. Perplexity declares thirty-two addresses in total and has an open dispute about crawling from others.
The thing every one of these tools does that most checkers do not is distinguish the check failed from the check could not run. A vendor feed that times out is not evidence against an address, and reporting it as one is how site owners end up blocking real crawlers and losing indexing. Start with the Bot IP Verifier if you are not sure which operator you are looking at, then move to the operator page for the detail. For a whole log file rather than one line, use the Access Log Bot Analyzer; for a list of addresses, the Bulk Bot IP Checker handles 200 in a pass.
Verification answers who is knocking. The last two tools in this category answer what your own site tells them when they arrive. The Robots.txt Tester takes a URL and a user-agent and reports which rule actually wins — not whether a rule exists, but which of several competing rules a crawler following RFC 9309 would apply, because the longest matching path wins rather than the first one written. That single detail accounts for most “but I blocked that” surprises.
The llms.txt Checker validates the newer file some sites now publish to point language models at their best content. It is worth being clear about what llms.txt is: a proposal, not a ratified standard, and no major AI operator has committed to obeying it. The checker tells you whether your file is well formed and what a parser would read from it, without pretending the file has authority it does not yet have. If your goal is actually to stop AI training crawlers, the AI Crawler Blocker writes the robots.txt and firewall rules from live vendor ranges, and our guide on how to block AI crawlers covers the trade-off between blocking training and staying visible in AI search.
Email is where the ground moved most in the last two years. Gmail replaced deferrals with permanent rejections for non-compliant bulk mail in November 2025, Outlook applied its own hard refusal the same month, and in May 2026 the IETF published RFC 9989 and its companions, replacing the original DMARC specification from 2015. A domain that was merely untidy in 2024 can now have its mail refused outright.
Thirteen tools cover that ground. If you do not know where to start, start at the Email Health Check, which runs the whole set against one domain and returns them side by side. Then go to the individual tool for whatever it flagged.
SPF (RFC 7208) lists who may send for your domain. The trap is not syntax, it is the hard ceiling of ten DNS-querying mechanisms across the entire flattened include chain. Add one more mail vendor and you can cross it without touching your own record, because the count includes everything your includes include. Past the limit the evaluation returns a permanent error, and a receiver that treats permerror as a failure will reject mail that would otherwise have passed. The SPF Checker resolves the chain and counts the lookups rather than guessing; the SPF Generator builds a record that stays under the limit in the first place.
A DKIM key (RFC 6376) is published at <selector>._domainkey.<domain>, and DNS gives you no way to list selectors — you have to know the name. That is why a DKIM check starts with a signed message: the selector is in the DKIM-Signature header. The DKIM Checker takes a selector and domain, fetches the published key, and reports the key type and size as well as whether the record parses.
SPF and DKIM both authenticate a domain, but not necessarily the domain a reader sees. DMARC closes that gap by requiring alignment: at least one of SPF or DKIM must pass and match the From header domain. The DMARC Checker validates a published record against RFC 9989, including the np tag that sets policy for subdomains that do not exist at all — the gap forgers used to walk through. The DMARC Generator writes a record from the policy you actually want, with the reporting addresses in the right format.
MTA-STS (RFC 8461) tells sending servers to require TLS to your domain, and it has three moving parts that have to agree: a TXT record at _mta-sts carrying a policy id, a policy file served at https://mta-sts.<domain>/.well-known/mta-sts.txt, and a valid certificate on that hostname. Change the policy without changing the id and senders keep using the cached old one. The MTA-STS Checker reads all three and reports which one disagrees.
BIMI puts your logo beside your messages, and it is gated: the domain needs DMARC at quarantine or reject with enforcement before anything else matters, the logo has to be SVG Tiny Portable/Secure rather than an ordinary SVG, and several mailbox providers additionally require a Verified Mark Certificate. The BIMI Checker checks the record, the logo file against the profile, and the certificate reference.
Perfect authentication does not help an address that has already earned a bad name. Check the sending address with the Sender IP Reputation tool and against the major DNSBLs with the IP Blacklist Check. If a specific message was rejected, paste its headers into the Email Header Analyzer, which reconstructs the delivery path, marks which hops can be trusted, and works out alignment itself rather than reprinting the receiving server’s verdict. Before you send at all, the Email Verifier checks an address is deliverable and the Temp Email Checker keeps disposable domains out of a signup form.
For the background on all of this, read how to check if your IP is failing SPF, DKIM and DMARC, what an IP reputation score is, IP reputation for bulk email, and the 550 RBL blocked sender fix guide.
Most outages that look mysterious are a DNS problem wearing a disguise. The nine tools here walk the path a browser takes: resolve the name, confirm the answer is the one you published, check the zone is signed correctly, then look at what the server presents when the connection finally opens.
The DNS Lookup queries nine record types, including PTR and CAA, which most free lookups leave out and which are exactly the two that break certificate issuance and mail reputation. When you have changed a record and it has not taken effect, the DNS Propagation tool asks resolvers in different parts of the world the same question at the same time. What that reveals is usually not slow propagation at all: it is TTL. A resolver that cached the old answer keeps serving it until the TTL you published expires, which is why lowering TTL before a planned change is the only thing that actually speeds a migration up.
If a zone is signed, the DNSSEC Checker walks the chain of trust from the root down and names the link that breaks. This matters because a broken DNSSEC chain does not fall back to the unsigned answer — a validating resolver returns SERVFAIL, so the domain simply stops existing for a large share of the internet while continuing to work fine from any resolver that does not validate. That asymmetry is why DNSSEC faults get misdiagnosed as hosting problems.
The SRV Record Lookup reads the _service._proto.name records (RFC 2782) that clients follow for SIP, XMPP, LDAP, Minecraft and autodiscovery, returning priority, weight, port and target — the four fields that decide which host a client actually tries first. For ownership, the WHOIS Lookup returns registration data. For what a visitor meets on arrival, the SSL Checker verifies the certificate and its chain, the Headers Analyzer inspects security headers such as HSTS, CSP and X-Frame-Options, and the Redirect Checker traces the full chain of status codes rather than just the final destination.
The CMS Detector answers a different question: what is this site built on. It reads only what the site publishes about itself — response headers, generator metadata, asset paths and cookie names — and shows you which of those signals produced the answer, so you can judge it rather than take it on faith. New to DNS? Start with how DNS resolves domain names to IPs.
Seventeen tools that take a single address and tell you what is actually known about it — and, just as importantly, what is only being guessed. Start with IP Geolocation for the estimate every commercial database would give, then move outward.
When that estimate is wrong — and for a large share of addresses it is — the Wrong IP Location tool shows you the difference between an estimate and a fact. It reads the registry record itself: the country the registry states, the size of the block your address sits in, the organisation it is issued to, and whether the holder has published an official geolocation file under RFC 9632. An address inside a block of 256 can be placed fairly precisely; one inside a block of several million cannot be, by anybody, and no correction form will change that. If your city is showing wrong, read why your IP shows a different city than where you live alongside it.
For the routing layer, ASN Lookup names the autonomous system that announces the address and who to contact about abuse, and ASN IP Ranges exports every block that network announces in iptables, nftables, nginx or Cisco syntax, with adjacent blocks merged so the rule count stays manageable. That is the tool you want when the answer is block the whole operator rather than one address — see how to block an entire ISP or hosting provider by ASN.
To classify an address rather than locate it: Cloud IP Check tests it against the major providers’ own published ranges, Tor Exit Detector checks the live relay list, Proxy Checker looks for proxy and VPN signatures, IP Fraud Score summarises abuse history, and Reverse IP Lookup finds the other domains sharing a server. If you want all of it at once, Deep IP Scan and the Global IP Report run the full set against one address and return a single readout.
For the path rather than the endpoint: Ping Test measures latency, Speed Test measures throughput, Port Scanner finds what is listening, and MTU Test finds the packet size ceiling — the usual culprit when small requests work and large uploads stall halfway with no error. At the hardware layer, MAC Address Lookup resolves a MAC to its vendor through the IEEE registry, and the MAC Address Generator produces random and locally administered addresses for lab work and address randomisation.
An IPv4 address is a 32-bit number, and a dotted quad is only one way of writing it down. Fourteen tools move between the representations, in both directions, because in practice you meet all of them.
Binary is the form subnet masks actually operate on, so IP to Binary and Binary to IP are the pair to reach for when a mask is not selecting what you expected. Decimal is the form a database should store, because integers sort and range-query correctly where strings do not — IP to Decimal converts both ways. Hex and octal mostly turn up in things trying not to be read: IP to Hex decodes the obfuscated links that appear in phishing mail, and IP to Octal covers the leading-zero case that has caused real parser bugs, because some libraries read 010 as octal 8 and others as decimal 10, and a filter that disagrees with the connecting library is a filter that can be walked past.
On the IPv6 side, IPv6 Expansion writes an address out in full and IPv6 Compressor shortens it by the RFC 5952 rules — which matter because two spellings of the same address will not match as strings, and that is why an allowlist entry sometimes silently fails. IPv6 to Binary shows all 128 bits grouped the way the address is written. IPv4 to IPv6 and IPv6 to IPv4 handle the embedded forms — the ::ffff: mapped notation that dual-stack servers write into logs for what was really an IPv4 connection, plus the compatible and 6to4 forms.
Three utilities for working with addresses in bulk: IP Extractor pulls every address out of a block of pasted text such as a log excerpt or an email header, IP Sorter puts a list into true numeric order rather than the alphabetical order a text editor gives you, and Random IP Generator produces test addresses. The Phone Number to IP Address Converter runs the same arithmetic on a phone number, which is a format novelty used for puzzles — not a lookup. No tool can find somebody’s real IP from their number, and that page says so on its face. New to the notation? Read how to read and understand IP address format and what an IPv6 address is.
Five tools for the calculations that sit under every allowlist, firewall rule and addressing plan. The Subnet Calculator and CIDR Calculator turn a prefix into its range, broadcast address and usable host count. The IP Range to CIDR tool solves the opposite problem, which is the one people actually get stuck on: a vendor gives you a start and an end address, and you need the minimal set of prefixes that covers exactly that span and nothing else — because ranges in the wild rarely land on neat prefix boundaries.
Once you have a list of blocks, the CIDR Overlap Checker finds the ones that contain each other, merges the adjacent ones, and tells you how many rules that saves. Fewer rules is not cosmetic: rule count is what slows a firewall down, and a merged list is also far easier to review. When something is being allowed or blocked and you cannot see why, the IP in CIDR Checker tests one address against a whole list and names the specific rule that matched.
If the subnetting itself is the unfamiliar part, what is a subnet mask, explained simply covers the ground, and how to block an IP range walks through turning start and end addresses into CIDR blocks in practice.
Modern tracking goes far beyond cookies. A site can identify your device from a combination of GPU rendering, audio processing, installed fonts, screen geometry and dozens of other details — a browser fingerprint that survives clearing cookies and switching to a private window. Twelve tools here split into two jobs: finding leaks, and measuring the fingerprint.
Start with Browser Leaks for the overview. Then WebRTC Leak Test, because WebRTC can reveal your real address even behind a VPN — it is the single most common way a VPN user is unmasked, and it happens in the browser rather than in the tunnel, which is why the VPN itself reports no problem. The Torrent IP Leak Test covers the case a browser test cannot reach at all: your torrent client announces itself to trackers and peers separately from your browser, so it can be leaking your real address while every browser-based test comes back clean. The test shows you the address a swarm actually receives. The Referrer Leak Test shows what your browser tells the next site about where you came from. For a fuller treatment, read how to check if your IP is leaking through a VPN and the WebRTC leak test and fix guide.
Canvas Fingerprint shows how your GPU renders text differently from every other device. Audio Fingerprint reveals your audio processing signature. JA3 TLS Fingerprint works one layer lower, identifying your client from the shape of its TLS handshake — before any JavaScript has run. Font Leak Tester shows which installed fonts a site can enumerate. Battery Checker checks whether the Battery API is exposing a value precise enough to be used as a short-lived identifier.
Two tools look for contradictions rather than values. Fingerprint Consistency checks whether your signals agree with one another — a mismatch between what your user-agent claims and what your rendering stack does is itself a strong identifier, which is why some anti-fingerprinting setups make you more distinctive. Timezone Audit is the sharpest version of that test: a browser clock in one country and an IP address in another is one of the easiest VPN tells there is. Finally, EXIF Data Remover strips the location and device metadata cameras write into photo files before you share them. Background reading: AI browser fingerprinting and how to clear your IP history and digital footprint.
Four tools read what your own device reports. Browser Info collects 25+ data points including User-Agent, WebRTC status, canvas hash and Do Not Track. Hardware Info reads GPU vendor and model via WebGL, plus CPU cores and RAM estimate. Screen Checker reports resolution, device pixel ratio, aspect ratio and refresh rate, and includes a dead-pixel test. Cookie Checker lists the cookies already stored, groups them as necessary, analytics or marketing, and lets you delete them individually.
Six developer utilities round the catalogue out, and all six are worth knowing about for one specific reason: they run entirely in the page. Base64 Encoder, Hash Generator (MD5, SHA-1, SHA-256, SHA-512), JSON Formatter, Punycode Converter, URL Encoder/Decoder and Password Generator never transmit what you type. That makes them safe for the thing people do with such tools anyway — pasting in a token, a config fragment or a customer record to check its shape — which is exactly what you should not do on a site that posts your input to a server.
Most people arrive here with a problem rather than a tool name. Find the line that matches what is actually happening and start there.
| What you are trying to do | Start here | Category |
|---|---|---|
| Something in my logs claims to be Googlebot and I do not believe it | Bot IP Verifier | AI Crawler |
| A Bingbot address fails reverse DNS but is on Microsoft’s list | Bingbot Verifier | AI Crawler |
| I blocked a path in robots.txt and crawlers are still fetching it | Robots.txt Tester | AI Crawler |
| I want to block AI training crawlers but stay in AI search results | AI Crawler Blocker | AI Crawler |
| My email is going to spam and I do not know which record is wrong | Email Health Check | |
| My SPF record returns a permanent error after adding a vendor | SPF Checker | |
| I need to write an SPF record that stays under the lookup limit | SPF Generator | |
| Check whether a DKIM key is actually published | DKIM Checker | |
| Check whether my domain will survive DMARC enforcement | DMARC Checker | |
| Write a DMARC policy record from scratch | DMARC Generator | |
| Senders are using an old MTA-STS policy after I updated it | MTA-STS Checker | |
| My logo is not showing next to my messages | BIMI Checker | |
| Work out why one specific message failed authentication | Email Header Analyzer | |
| My sending IP has been refused by a mail provider | IP Blacklist Check | |
| My site is down and I do not know why | DNS Lookup | DNS |
| I changed a DNS record and it has not taken effect yet | DNS Propagation | DNS |
| My domain resolves for me but not for some visitors | DNSSEC Checker | DNS |
| A client cannot autodiscover my SIP or XMPP service | SRV Record Lookup | DNS |
| Confirm a certificate before launch | SSL Checker | Domain |
| Audit HTTP security headers | Headers Analyzer | Domain |
| Trace a redirect chain | Redirect Checker | Domain |
| Find out what platform a website is built on | CMS Detector | Domain |
| Find my public IP and where it resolves to | IP Geolocation | Network |
| Sites think I am in the wrong city | Wrong IP Location | Network |
| Find out who owns an IP address | ASN Lookup | Network |
| Block or allow an entire network in a firewall | ASN IP Ranges | Network |
| Check whether an address belongs to a cloud provider | Cloud IP Check | Network |
| Find open ports on a host | Port Scanner | Network |
| Diagnose a slow or dropping connection | Ping Test | Network |
| Fix large uploads that stall halfway | MTU Test | Network |
| Store IP addresses in a database so they sort correctly | IP to Decimal | Converters |
| My IPv6 allowlist entry is not matching the same address | IPv6 Compressor | Converters |
| My logs show addresses starting with ::ffff: | IPv6 to IPv4 | Converters |
| Pull every IP address out of a pasted log or header | IP Extractor | Converters |
| Turn a start and end address into firewall blocks | IP Range to CIDR | CIDR |
| Work out which allowlist rule let an address through | IP in CIDR Checker | CIDR |
| Plan an addressing scheme | Subnet Calculator | CIDR |
| Check whether my VPN is actually hiding me | WebRTC Leak Test | Privacy |
| Check what address my torrent client is exposing | Torrent IP Leak Test | Privacy |
| See everything my browser gives away | Browser Leaks | Privacy |
| Strip location data out of a photo before sharing it | EXIF Data Remover | Privacy |
| Format or validate an API response | JSON Formatter | Developer |
Working through a real fault, in order: confirm what the outside world sees with the DNS Lookup, check whether a resolver is still serving the old answer with DNS Propagation, check the certificate with the SSL Checker, confirm the port is actually open with the Port Scanner, then measure the path with Ping. Five checks in that order rule out most of what breaks a site.
92, across nine categories: AI Crawler, Bot Verification & Crawl Rules (12), Email Authentication & Deliverability (13), DNS, Domain & Web Infrastructure (9), Network Diagnostics & IP Intelligence (17), IP Address Converters (14), Subnet, CIDR & Range Planning (5), Privacy & Leak Testing (12), Browser & System (4) and Developer Utilities (6). The jump links at the top of this page go straight to any of them, and the symptom table above is the fastest route if you know the problem but not the tool name.
The newest group is the email authentication set — Email Health Check, SPF Checker and SPF Generator, DKIM Checker, DMARC Generator, MTA-STS Checker and BIMI Checker — built around RFC 9989, which replaced the 2015 DMARC specification in May 2026. Alongside them: DNS Propagation, DNSSEC Checker and SRV Record Lookup for DNS; Robots.txt Tester, llms.txt Checker and CMS Detector for the crawl and site layer; IPv6 Compressor, IPv4 to IPv6, IPv6 to IPv4, IPv6 to Binary, Binary to IP and IP Extractor for address work; and Torrent IP Leak Test and Wrong IP Location.
Because no two operators can be checked the same way. Google publishes five range files and documents reverse DNS; Microsoft documents reverse DNS but its published list contradicts it on at least one subnet; OpenAI publishes four files with overlapping prefixes and no reverse DNS; Anthropic publishes one file covering three crawlers; Perplexity declares thirty-two addresses in total. A single generic checker has to flatten all of that into one answer, and flattening it is how a real crawler gets reported as fake. Start at the Bot IP Verifier if you do not know which operator you are looking at.
Start with the Email Health Check, which runs SPF, DKIM, DMARC, MTA-STS and BIMI against your domain in one pass and shows which of them is the problem. Then go to the individual tool for the detail: the SPF Checker counts your DNS lookups against the limit of ten, the DMARC Checker validates the policy record, and the IP Blacklist Check tells you whether the sending address itself has picked up a bad reputation. If one specific message was rejected, paste its headers into the Email Header Analyzer, which usually names the reason outright.
The DNS Propagation tool asks resolvers in different regions the same question at once, so you can see which ones are still serving the old answer. Usually the answer is TTL rather than propagation: a resolver keeps the old record until the TTL you published expires, which is why lowering TTL before a planned change is the only thing that reliably speeds a migration up. If the domain resolves for you but fails entirely for some visitors, that is a different fault — run the DNSSEC Checker, because a broken signing chain makes validating resolvers return SERVFAIL rather than falling back.
Look the address up with the ASN Lookup to find the autonomous system that announces it, then feed that AS number into ASN IP Ranges. It returns every block the network announces and exports them in iptables, ipset, nftables, nginx, Apache, Cisco, MikroTik or pfSense syntax, with adjacent blocks merged so the rule count stays manageable. If you only have a start and an end address rather than an AS number, use IP Range to CIDR instead.
Four, in order. IP Geolocation to see the address sites are given. WebRTC Leak Test for the most common unmasking route, which happens in the browser rather than in the tunnel, so the VPN itself reports nothing wrong. Timezone Audit for the mismatch between your browser clock and your apparent country, which is one of the easiest tells there is. And if you use a torrent client, the Torrent IP Leak Test, because that traffic announces itself separately from your browser and can be leaking while every browser test comes back clean.
The Wrong IP Location tool tells you whether it is fixable at all, which is the part most guides skip. It reads the registry record for your address and shows the size of the block you are in. If that block is small, the location attached to it is describing something real and a correction is genuinely worth filing. If it covers millions of addresses, no database can place you inside it and no correction form will change that. It also shows whether your provider has published an official geolocation file, which is the mechanism the databases would read if it existed.
No, and neither can anything else. A phone number belongs to a carrier’s numbering plan and an IP address is assigned by an internet provider; there is no public mapping between the two. The Phone Number to IP Address Converter does something different — it rewrites the digits of a number as an address, which is a format conversion used for puzzles and obfuscation. It says so on the page rather than letting anyone assume otherwise.
No. Every tool runs in the browser at the URL you visit. Several of them — the hash generator, JSON formatter, Base64 encoder, URL encoder, password generator and the fingerprint tests — never send your input anywhere at all; the work happens in the page. Where a tool does need an external lookup, such as DNS, WHOIS or a registry record, the page says so.
Yes. Every tool on TrustMyIP is free with no account, no subscription, and no hidden usage limits. The client-side tools — hash generator, JSON formatter, Base64 encoder, URL encoder, password generator and the browser fingerprint tests — run entirely in your browser, so your data never leaves your device.
Client-side tools (browser info, hardware, screen, cookie checker, hashing, encoding, formatting) process everything locally and send nothing. Server-side tools (DNS, WHOIS, SSL, registry lookups, email record checks) send only the domain or address you enter — never anything else about you. We do not log queries or sell data.
Yes. All 92 tools are responsive and work on iPhone, Android, iPad and any mobile browser. A few hardware features — the Battery API, some WebGL detail — are limited or absent on certain mobile browsers, and the tools that use them say so on the page rather than reporting a blank as a result.
Follow this order: Browser Leaks for the overview, then WebRTC Leak Test, Canvas Fingerprint, Audio Fingerprint, JA3 TLS Fingerprint, Font Leak Tester and Cookie Checker. Finish with Fingerprint Consistency and Timezone Audit, because contradictions between your signals are themselves identifying — that is the step most audits leave out.
From IP lookup and DNS diagnostics to email authentication, leak testing and developer utilities — everything you need for network troubleshooting, deliverability, privacy testing and web development in 2026.