1
6
trulysoulless

@lemmy.world

trulysoulless 10 points 2 days ago

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!

path: 0 24351076 24351796, hotness: undefined, score: 10, children: 1
trulysoulless 4 points 2 days ago

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

path: 0 24352762 24353742, hotness: undefined, score: 4, children: 0
trulysoulless 2 points 2 days ago

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

path: 0 24354302 24354366, hotness: undefined, score: 2, children: 0
trulysoulless 2 points 2 days ago

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

path: 0 24354185 24354355, hotness: undefined, score: 2, children: 2
trulysoulless 2 points 2 days ago

Oh thanks, I'll fix that

path: 0 24351947 24352016, hotness: undefined, score: 2, children: 0
trulysoulless 1 point 2 days ago

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

path: 0 24353075 24353777, hotness: undefined, score: 1, children: 0

thanks for using Leebra!

go to feed...