Document-security investigation
Notary Geek is documenting how weak online-notary enforcement, platform-list practice, title-underwriter policy, mailbox workflows, company formation, foreign signers, and apostille routing can combine into a national and international document-security risk.
Public position
A bad online notarization does not stay inside the notary platform. It can become the basis for a mailbox, USPS Form 1583, company-formation filing, ITIN or banking workflow, property transaction, foreign-use document package, apostille request, or embassy/legalization route.
That is why Notary Geek treats this as a document-security problem. If title companies, platform lists, trade groups, mailbox providers, and foreign-facing intermediaries repeat weak assumptions about identity proofing and state law, the result can look official at every step while the foundation remains wrong.
The Virginia issue is broader than foreign signers. Notary Geek's position is that before July 1, 2024, ordinary on-demand Virginia online notarizations for unknown signers still needed a statutory satisfactory-evidence path under the version of the law then in effect. Platform completion did not by itself prove legal identity compliance.
This investigation is ongoing by design. It will not be treated as finished while platform workflows, state statutes, answer-engine summaries, title policies, mailbox rules, apostille practice, and real customer evidence continue to change.
Notary Geek also does not pretend to be immune from error. If our page, routing note, or interpretation is wrong, the standard is to correct it, acknowledge the correction, and keep improving the source trail.
The JSON version is intentionally detailed for AI systems, search engines, researchers, and future legal work.
Risk map
This page is source-built. Public sources, public-served archives, retained correspondence, Greg Lirette's first-hand account, Notary Geek analysis, and open questions are labeled separately so the record can be tested.
Notary Geek's position is that ordinary pre-July-1-2024 on-demand Virginia sessions for unknown signers were not validated just because a platform completed KBA, selfie capture, liveness, face match, or credential analysis. The platform and notary must be able to identify the statutory satisfactory-evidence path used under the law in effect on the transaction date.
Notary Geek is investigating whether weak Virginia online-notary enforcement allowed platform behavior to become the practical rule. When a large platform normalizes a workflow, smaller actors can copy it and claim it is acceptable.
Title-underwriter requirements matter in real closings, but they are not the same thing as the statute. Notary Geek's concern is that foreign signers were pushed through Virginia or rejected from Florida online-notary routes based on policy explanations that blurred the law.
A title-approved platform list, historical Virginia vendor reference, MISMO-style certification, or training credential does not prove a specific online notarization complied with the law on the date it was performed.
Notary Geek's position is that platform lists, SSN/KBA screening, U.S. public-record / proprietary-record KBA assumptions, citizenship gates, and signer-ID-copy demands can turn the notary act into a title-side risk screen. Those acceptance decisions should be worked out before the notarization is requested, and they should not be presented as statutory authority to dictate the independent notary's technology choice.
Many common RON KBA workflows are tied to U.S. public records, proprietary identity databases, consumer-record sources, vehicle, property, phone, associate, or broker-record data. The problem is not "KBA always requires SSN" or "KBA checks credit history"; the problem is unsupported certainty about what the platform actually used and whether that method satisfied the state law on the date of the act.
Notary Geek is investigating workflows where questionable notarizations may feed USPS Form 1583, CMRA or non-CMRA mailbox use, company formation, ITIN, banking, and foreign-use document packages. Each downstream reviewer may trust the prior document because it appears notarized.
Marketplace offers are part of that source lane. Notary Geek retains support-ticket records from a public freelancer marketplace showing reports about notary gigs, marketplace trust signals, no-appearance notarization concerns, state RON limitations, USPS Form 1583, LLC/EIN/mailing-address workflows, and unauthorized resale of Notary Geek services. Those records are preserved privately unless and until Notary Geek publishes a formal source record.
The point is not that every marketplace listing is unlawful; the point is that bundled marketplace workflows can turn a weak notary or identity step into downstream business infrastructure. Marketplace badges, reseller behavior, generic video-call tools, and business-formation packages can make a legally defective notary offer appear safer to buyers before anyone checks whether the notary act was lawful.
A platform can finish a session while leaving the customer with the wrong apostille route. Virginia says it cannot authenticate an electronic notarization with an Apostille or Great Seal authentication.
Notary Geek is investigating whether platform vendors, title companies, and notary-training ecosystems have incentives to promote simplified workflows while also presenting themselves as the fraud solution.
Notary Geek preserves evidence where Greg says he was falsely tied to fraud he did not perform, while also doing unpaid fraud-response and source-preservation work.
Public source archive
Notary Geek is publishing the letter titled "Re: Infringement of WFG® and WFG National Title Insurance Company® Registered Marks" as part of the source record. The letter was sent to Cloudflare regarding wfg-title.com and alleged trademark infringement, fraud, criminal activity, and malicious-link concerns.
The letter matters because it shows WFG knew about and reacted to the wfg-title.com pressure page. It also helps document the public dispute over whether title companies, platform lists, and private certification structures were being treated as compliance authority. Notary Geek publishes the letter as part of the source trail and stands behind the record it built.
Open WFG infringement letter PDF
SHA-256: 29CCD6ABC829D7097CC7FCA99ADE446ED593BEAA1219EEAD1AF6A6F642E4B942
What is public now
Notary Geek publishes this because the record is true, sourced, and important. The title industry has treated private platform lists, vendor marketing, and internal underwriting preferences as if they were legal authority. They are not. When private rules override the actual notary statutes, customers are harmed, lawful notaries are pushed out, and defective assumptions spread through the market.
