Skip to content

Bought a dropped domain. Previous owner's SSL cert still valid. Concern?

Domain Names by mediaaustin 15 replies 859 views
#1

Bought a dropped domain from an auction last week. Previous owner's SSL cert from Time4VPS is still valid for another 60 days. My server, their certificate, no revocation showing in CT logs yet.

For what it's worth, this is not purely academic. Browsers still trust it. Mail servers might too. The previous owner could theoretically still present that cert if they control any lingering DNS or CDN edge. SPF and DKIM are clean on my end, but the certificate transparency lag is real.

Has anyone mapped typical revocation delays? The RFC 6962 ecosystem feels slower than blocklist propagation, and that is saying something.

SPF, DKIM, DMARC — holy trinity ✉️
#2
mediaaustin said:
Previous owner's SSL cert from Time4VPS is still valid for another 60 days

Just use certbot. Skill issue.

But seriously, OCSP stapling is dead, CRLSets are a joke, and browsers cache "good" longer than "bad." The previous owner could MITM anyone still resolving the old A record. Just use X.509 renewal automation and stop buying other people's problems.

oops: 0000 [#1] SMP
#3

Anyway I had this exact thing in 2023. Bought a dropped domain, previous owner's cert valid for 89 days. Idk why I do this but I wrote a cron that polled the CT logs every hour and graphed it. Took 11 days for a precertificate to show revocation.

While true; do
curl -s "https://crt.sh/..." | jq.
Sleep 3600
Done

3am code never dies. 💀

builds at 3AM, sleeps at noon
#4

This is why I just don't buy dropped domains anymore. Too many weird edge cases. The cert thing, sure, but also the reputation hit with Google. Took me six months to get out of the "this site may be hacked" sandbox on a dropped .com I bought in 2022.

#5
prague1983 said:
Just use certbot. Skill issue.

I have certbot running. That's not the point. The point is a third party still holds a cryptographically valid claim to my hostname and the revocation infrastructure is too slow to matter.

tallinnying said:
Took 11 days for a precertificate to show revocation

11 days is actually faster than I expected. Did you ever see OCSP respond revoked before the CT log caught up? In my current case the OCSP responder still says "good" too.

SPF, DKIM, DMARC — holy trinity ✉️
#6
mediaaustin said:
Did you ever see OCSP respond revoked before the CT log caught up?

Never. In my case the OCSP "good" outlasted the CT precertificate by about 36 hours. So you had this window where the log said revoked but live validation still passed.

Also hi from the night shift, I am running the same curl cron again on your domain now. Will DM you if I see movement.

builds at 3AM, sleeps at noon
#7

I buy dropped domains for a side project and this thread is making me anxious. Never checked for lingering certs. How do you even find the issuer quickly? Just CT logs or is there a better way?

Currently paying Time4VPS €4.50 for a small VPS in Vilnius but never used their SSL offerings.

#8
DragonMark said:
Reputation hit with Google

Google sandbox is not SSL related though. That's domain history, backlinks, spam score. Different problem.

web20 said:
How do you even find the issuer quickly?

Crt.sh or censys. If you know the domain you know the certs. This is public data.

oops: 0000 [#1] SMP
#9

In France we have a similar problem with ANSSI and their certificat électronique rules for government sites, but for commercial hosting nobody cares. I manage fifty domains for clients and I see this maybe twice a year. My solution: I contact the old host directly. Time4VPS in Vilnius, they answer in 24 hours usually, I ask them to revoke. It works.

Vive la résistance... électrique
#10

This.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft