Paste the URL of an app you own or have permission to test. Malinois checks what a normal visitor can see — security headers, public configuration, client-side secrets, and data-store references — then explains the result in plain language. No login, exploitation, or private-network scanning.
No reviews yetBe the first to leave a review for Malinois
Maker
📌
I made Malinois because AI builders shorten the path to a live app, but they do not keep watching the public surface after launch.
The first check is free, passive, and takes about 15 seconds. You confirm that you own the app or have permission before it runs. There is no email required for the check itself.
I am looking for direct feedback on three things:
1. Is the report specific enough to act on?
2. Which checks feel useful, and which feel noisy or misleading?
3. Would you use this for an app you actually run? If not, what would stop you?
For the first 20 owner-verified apps, Malinois offers one app of weekly monitoring for 30 days. There is no card and no automatic billing. This is a real operating limit, not a general signup trial.
I do not have enough genuine usage to claim conversion, accuracy, or platform statistics yet. I would rather learn from concrete feedback than invent proof.
Report
This looks genuinely useful for quick security spot-checks. One idea: add a way to compare results over time so you can see if a header got dropped or a new public file appeared after a deploy. That would turn a one-off scan into something you can actually track.
Report
Maker
Thanks — you’re right. A one-off scan is only a snapshot.
For monitored apps, Malinois re-checks the public surface daily, compares each scan with the prior baseline, and alerts only when a new serious issue appears. The dashboard also keeps an inspection-history report so you can show what changed over time.
The free check remains a snapshot on purpose; the value of monitoring should be seeing a regression after a deploy, not receiving the same warning repeatedly. I should have made that distinction clearer in the launch copy. If you try it, I’d especially value feedback on whether the history makes the change easy to understand.
Such a promising launch—congrats on Malinois! Free external security checks for AI-built web apps is a clever idea. Wishing you a strong Product Hunt day! 🚀
This looks genuinely useful for quick security spot-checks. One idea: add a way to compare results over time so you can see if a header got dropped or a new public file appeared after a deploy. That would turn a one-off scan into something you can actually track.
Thanks — you’re right. A one-off scan is only a snapshot.
For monitored apps, Malinois re-checks the public surface daily, compares each scan with the prior baseline, and alerts only when a new serious issue appears. The dashboard also keeps an inspection-history report so you can show what changed over time.
The free check remains a snapshot on purpose; the value of monitoring should be seeing a regression after a deploy, not receiving the same warning repeatedly. I should have made that distinction clearer in the launch copy. If you try it, I’d especially value feedback on whether the history makes the change easy to understand.
Pazi
Such a promising launch—congrats on Malinois! Free external security checks for AI-built web apps is a clever idea. Wishing you a strong Product Hunt day! 🚀