You’re right, I must have totally misread that page I linked. My resolver was returning a bogus result, I toggled DNSSEC validation, and didn’t dig much further. Looks like it‘s an issue with my resolver on this domain. Odd, because I haven’t touched my configuration in ages and I haven’t seen this problem before.
Isn't this just the DNS reporting to you that DNSSEC isn't configured for retracted.com and netlify.com at all? That's not a misconfiguration; it's the right configuration.
https://dnssec-analyzer.verisignlabs.com/wattenberger.com