Comparing an unparseable OCSP response for one certificate (dated 2026-09-15 14:36) and a parseable one for another (dated 2026-09-17 19:31), Sectigo have removed that NULL parameter that the forum/Bugzilla posters believed to be at issue. I have no personal opinion about who or what is at "fault" or whether it was compliant, though.