Inheriting a Bad Name: The Hidden Risk of Buying Domains
October 31, 2025 ・ Posted by stackDNS.io
When we launched our email infrastructure service, we thought we had full control: DNS, SPF, DKIM, DMARC, TLS, Rspamd, SMTP logs — all airtight.
But something odd happened.
A brand-new domain — bought from a reputable registrar — couldn’t deliver emails reliably. Gmail marked it as spam. Outlook dropped messages. No bounce, no NDR. Just silent rejection.
After hours of debugging, we discovered the problem: the domain had a past life. A bad one.
What Your Registrar Doesn’t Tell You
Most domain registrars (especially budget ones like PorkBun) don’t vet or disclose domain history. That means you can unknowingly buy a domain previously:
- used for phishing or malware
- flagged by Spamhaus or SURBL
- rate-limited or downgraded by Gmail or Outlook
And the worst part? These issues don’t show up until you start sending email. By then, you're already on a blacklist you didn’t even know existed.
There’s no warning at checkout. No visible indicator of past abuse. You’re flying blind.
The Real-World Cost
If you’re a startup, early-stage org, or freelancer, this matters more than ever. Your domain is your reputation.
A tainted domain can kill your email before you even start. Password resets don’t arrive. Partner emails go unanswered. You look unreliable — even if everything on your side is configured perfectly.
This isn’t just a technical issue. It’s a trust issue. It’s a market failure.
What We're Building — and Why
This experience is one reason we are building stackDNS.io: a nameserver and email platform focused on transparency and user control.
As part of our infrastructure:
- We plan to check domain reputation at onboarding
- We’ll surface spam scores and delivery logs to users, not hide them
- We aim to build tools to test and validate domains before purchase
Owning your infrastructure should mean understanding it. And that starts with knowing the truth about your domain.
Follow-Up: What Happened After
After we published this article, we received no response or acknowledgment from PorkBun — no explanation, no apology.
Within 24 hours of successfully disputing the transaction, the domain verifyme.lol was taken back by PorkBun.
Shortly after, our emails to info@verifyme.lol began failing with DNS errors: Gmail flagged the MX lookup with SERVFAIL, indicating a broken or missing mail configuration.
This confirms our core point: infrastructure providers should not operate this carelessly. Users deserve transparency — before, during, and after a domain purchase.