Skip to content
VetThisVendor

About

Last updated

Who built this

I am Jose Pollman. I build small, single-purpose, free tools and run them myself — this one, notspoofed.com for email authentication, whattofixfirst.com for page speed, subcovered.com for certificate-of-insurance tracking, and knowyourmouth.com.

There is no company behind this and no team. Everything on the site was written and is maintained by one person, which is worth knowing in both directions: nobody is upselling you, and when something here is wrong it is wrong because I got it wrong. Corrections go to hello@vetthisvendor.com and I answer them.

I wrote up the fraud this site was built around — The Most Common Invoice Fraud Passes Every Check I Builton Medium.

Why it exists

The usual invoice fraud is not a fake company. It is a real supplier whose mailbox was compromised, sending a real invoice for real work, with one field changed: the bank account. Every automated check passes, because everything except the account is genuine. That is the case this site was built around, and it is why no result here ever says “safe to pay” and why every result repeats the same instruction — confirm the account by phone, on a number you already had.

Since 9 October 2025, banks across the euro area have had to run Verification of Payee: they check the account holder’s name against the IBAN before you confirm a transfer. It is a real improvement and it answers the one question this site cannot — does the account actually belong to them. It also says nothing about whether the company is in liquidation, struck off, sanctioned, or a domain registered three weeks ago. Those are the questions here. What Verification of Payee covers goes through it properly.

Everything else was a matter of where the answers live. The VAT registry, an IBAN validator, three sanctions lists, the company register and the domain’s DNS records are five different places. Checking all five by hand takes ten minutes, so in practice people check one, or none. This runs them from one submission.

How each check works

VAT / registration number. The format is validated locally first, per country, so a mistyped number is caught before anything is asked of a registry. The number then goes live to VIES, the European Commission’s own service, for EU and Northern Ireland numbers. Thirteen countries are additionally read against their own national register, which is the part that matters: VIES answers only whether a number is registered, and a company in liquidation, insolvent or struck off usually still has a VAT number that resolves in VIES perfectly cleanly. The national registers are also up on the days VIES is not. GB numbers get the official check digit verified locally and no registry lookup — see below.

IBAN. Structure and the MOD-97 checksum, computed here, with no third party involved and nothing transmitted. This is arithmetic: it catches the transposed pair of digits that proofreading misses, and it cannot tell you who owns the account. The bank the account is held at is named where the country publishes its bank codes.

Sanctions screening. A daily local copy of three lists — the EU consolidated list, the UK list from OFSI, and the US SDN list from OFAC — is screened by fuzzy name similarity. The threshold was measured rather than guessed, and it is set so that a false positive is rare, because a false sanctions match gets acted on. Both the name you typed and the name the registry returned are screened, since an invoice often carries a trading name and the list carries the legal one.

Company register. Companies House for UK suppliers, the official French recherche-entreprises for French ones. Both are text searches over a name, not a lookup by number, so a single company is named only when exactly one result matches after normalisation — otherwise you get the near misses to choose between. For a country neither register covers, nothing is searched and the card says so, rather than reporting that your Latvian supplier is “not on the UK register”.

Sending domain. SPF, DMARC policy, MX records and the domain’s registration age, read from public DNS and RDAP. Registration age is weighted above the email authentication on purpose: someone registering a lookalike domain configures SPF and DMARC properly, because they need the invoice to arrive, so the impersonator often authenticates better than the twenty-year-old real supplier. The age is the field that separates them.

What it deliberately does not do

Why it is free

It costs almost nothing to run. It sits on a server that was already there for other things, reads public data sources, and stores nearly nothing. There is no funding to justify and nothing to upsell, so there is no reason to put a check behind a signup form.

There are no ads and no trackers beyond a self-hosted, cookieless page counter. See privacy for exactly what that means.

Contact

hello@vetthisvendor.com — corrections, questions, anything about the tool.

privacy@vetthisvendor.com — deleting a saved result before it expires, or any question about what is stored. See privacy.

Sources

What you get, country by country is the same information as a table, and it is generated from the checks themselves rather than written by hand, so it cannot fall behind what the tool actually does.