I’ve experienced old.* misbehaving with TLS before, where the cert was either not the right name or wasn’t yet valid (12mo ago perhaps) - I’m wondering if it ma

I’ve experienced old.* misbehaving with TLS before, where the cert was either not the right name or wasn’t yet valid (12mo ago perhaps) - I’m wondering if it may be related to an earlier crawl where that has happened