Who checks certificates on domains listed for sale?

[nicenicnicenic is verified member.]

When a domain points to a marketplace lander, the marketplace may handle HTTPS without the owner doing anything.

The report below raises a useful question for sellers: do you monitor certificates yourself, or expect the lander provider to handle that?

Has anyone had to ask a marketplace about a certificate they didn’t recognize?

Google’s report:

Chrome's Response to Recent ccTLD Registry Hijacks

Following recent third-party domain hijacks affecting the .gh, .sl, and .as country-code top-level domains (ccTLDs), Chrome immediately blocked unauthorized HTTPS certif…

blog.google

 

[ElhagMousab]

I check them myself, mainly because a lander provider only really covers the names it serves. For my own portfolio I have a habit of scanning the public certificate transparency logs every couple of weeks, since that is where a stranger proves they got a certificate issued for a name I own, and it shows up long before anything looks different on the site itself. Parking and marketplace landers usually serve a shared or wildcard certificate from the provider's CDN, so the issuer named in the browser is rarely something I recognise anyway. The one time something looked odd on a name I had parked, I asked the marketplace and they came back confirming it was theirs, which took a couple of days. What I would not count on is the lander provider noticing a certificate issued somewhere else entirely, because watching for that is not what their tooling is built to do.