How to Reach Fake Addresses
Reaching Fake Addresses happens through one address: hello@fakeaddresses.com. That single inbox covers every category of inquiry the site can currently handle — a bug report, an API question, a press request, a correction to a guide, or a report of someone misusing generated output — because there is no dedicated ticketing system, live chat widget, or phone line behind a project this size.
A response should be expected within a few business days for most messages. This is not a staffed support desk with guaranteed response-time targets, and urgent matters involving an active crime should go to the appropriate authority directly rather than waiting on an email reply from Fake Addresses, which has no investigative or enforcement authority of its own.
Messages sent to hello@fakeaddresses.com are read by the person maintaining Fake Addresses, named on the about page, not routed through an automated triage system or a third-party support vendor. This keeps the contact channel simple and accountable — one address, one person reading it, rather than a form that disappears into a queue with no visible owner. That is a deliberate trade-off: it will not scale to a large support volume, but every message that does arrive gets read by someone who actually understands how the generator works.
What to Include in a Support or API Request
A support or API request to Fake Addresses gets answered faster with a few specific details included up front: the endpoint or page involved, the exact request made (including the seed and dataset parameters if relevant), the response received, and what was expected instead. A vague "the API doesn't work" message takes longer to resolve than one with a reproducible example.
For a bug report on the generator itself — an address that fails format validation, a suffix abbreviation that looks wrong, a ZIP code and city that disagree — the specific generated record should be included, ideally with its seed. That lets the issue be reproduced and checked against the validation harness directly, rather than investigated from a description alone.
Rate-limit questions should include the approximate request volume and pattern involved. The published 60-requests-per-minute anonymous limit is enforced automatically, and a specific, higher-volume use case is easier to evaluate with real numbers attached than with a general request for more access.
None of this is required to get a response from Fake Addresses — a short message is still read and still answered. A reproducible example is simply what turns a report into a fix faster, rather than a longer back-and-forth to reconstruct the same details after the fact.
Press, Legal and Misuse Reports
Press inquiries about Fake Addresses — requests for comment, questions about the data behind a guide, interview requests — go to the same hello@fakeaddresses.com address. Every message in this category is read directly by the site's named maintainer, not forwarded through a communications team, because none exists at this size.
Legal inquiries, including questions about the freely usable output license, the Acceptable Use policy, or a specific claim made in the flagship § 1342 guide, should also start at that address. Fake Addresses is not able to provide legal advice in response, consistent with the disclaimer published on this site, but can clarify what a specific page does and does not claim.
Misuse reports — a case where generated output is being used to defraud a real system — should be sent the same way, with as much detail as is safely available. Reports involving an active crime should also go to local law enforcement or the U.S. Postal Inspection Service directly, since Fake Addresses can restrict API access to an abusive pattern but has no power to investigate or prosecute anything itself.
Every category above shares one inbox on purpose. A project this size does not benefit from routing complexity, and a single, monitored address is more reliable than a form that promises categorization it cannot actually deliver.
Frequently asked questions
Is there a phone number for Fake Addresses?
No. Fake Addresses is reachable only by email, at hello@fakeaddresses.com. There is no phone line or live chat, which keeps the single contact channel simple and directly monitored by the person maintaining the site rather than routed through a call center.
How fast will Fake Addresses respond to a message?
Most messages get a response within a few business days. There is no guaranteed support-time commitment behind a project this size, and anything involving an active crime should go to the relevant authority directly rather than waiting on a reply.