Thanks, I’ll fix that. I’ll add a filter for known privacy-proxy and registrar abuse domains

Yep, I’m a solo dev and I use AI assistance while building this. So, I should’ve been upfront about it. The code’s all reviewed, tested, and MIT-licensed, so it’s fully auditable. I’ll add a disclosure to the README

Thanks, gotcha. I figured marking those cases as inconclusive makes a lot more sense than treating them as failures. It should cut down on false alarms from catch-all and greylisted servers while still keeping the results reliable. Since I’m already checking MX, SPF, and DMARC, I should have enough confidence without being overly aggressive

Xd, prism is basically un-googleable that one’s on me cause there is not a great SEO foresight. The name was mine though

Oh thanks, I’ll fix that

Hiya, love that you actually tested it. That’s exactly the kind of 30-second recon it’s built for. The “missing security headers” check catches a surprising number of sites.

If there’s a module or source you’d want added, I’m genuinely taking requests that’s how the roadmap gets shaped. Thanks for trying it!