<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Benjamin Frank</title>
    <description>The latest articles on DEV Community by Benjamin Frank (@bennidev).</description>
    <link>https://dev.to/bennidev</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3669198%2F7f1ee168-6674-4cb2-b38e-f62c5a2ac034.jpg</url>
      <title>DEV Community: Benjamin Frank</title>
      <link>https://dev.to/bennidev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bennidev"/>
    <language>en</language>
    <item>
      <title>I built a website security scanner (because I kept shipping insecure projects)</title>
      <dc:creator>Benjamin Frank</dc:creator>
      <pubDate>Thu, 18 Dec 2025 15:06:05 +0000</pubDate>
      <link>https://dev.to/bennidev/i-built-a-website-security-scanner-because-i-kept-shipping-insecure-projects-1d67</link>
      <guid>https://dev.to/bennidev/i-built-a-website-security-scanner-because-i-kept-shipping-insecure-projects-1d67</guid>
      <description>&lt;p&gt;I’m a solo developer, and over the last year I kept running into the same problem:&lt;/p&gt;

&lt;p&gt;I’d ship projects thinking “I’ll secure this properly later”&lt;br&gt;
and then… later never came.&lt;/p&gt;

&lt;p&gt;If I’m being honest, my cybersecurity knowledge isn’t great. I know enough to be dangerous, but not enough to feel confident. I’d regularly forget things like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;missing or misconfigured security headers&lt;/li&gt;
&lt;li&gt;weak TLS / SSL setups&lt;/li&gt;
&lt;li&gt;basic server or app misconfigurations that should be caught early&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Most of these issues aren’t advanced attacks — they’re just things you miss when you’re focused on shipping features.&lt;/p&gt;

&lt;p&gt;So instead of pretending I’d magically get better at security overnight, I decided to build a tool that helps catch these problems for me.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6554iaqzxxmiy78y0rfo.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6554iaqzxxmiy78y0rfo.png" alt="Example Scan with DataFast" width="800" height="476"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why I built SecureNow&lt;/strong&gt;&lt;br&gt;
SecureNow is a website security scanner that checks for common vulnerabilities and gives you a clear report with fix recommendations.&lt;/p&gt;

&lt;p&gt;The goal is not to replace professional pentesting.&lt;br&gt;
&lt;strong&gt;It’s meant to be:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a fast baseline security check&lt;/li&gt;
&lt;li&gt;something you can run before or after deploying&lt;/li&gt;
&lt;li&gt;useful for developers and small teams who don’t have a security expert on hand&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Basically: “Did I forget something obvious?”&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What it checks&lt;/strong&gt;&lt;br&gt;
Some of the features I thought were pretty cool (and honestly useful for my own projects):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Security header checks (CSP, HSTS, etc.)&lt;/li&gt;
&lt;li&gt;TLS / SSL configuration analysis&lt;/li&gt;
&lt;li&gt;Open port scanning (surprisingly, a lot of sites still expose things they shouldn’t)&lt;/li&gt;
&lt;li&gt;Rate limit detection&lt;/li&gt;
&lt;li&gt;API route checking&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Clear explanations + suggestions on how to fix issues&lt;/p&gt;

&lt;p&gt;Nothing intrusive, no exploit-style scanning — just automated checks that surface common problems.&lt;/p&gt;

&lt;p&gt;Who this is for (and who it isn’t)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SecureNow is designed for:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;solo developers&lt;/li&gt;
&lt;li&gt;indie hackers&lt;/li&gt;
&lt;li&gt;small teams&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;people shipping fast and trying not to break things (or expose them)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It’s not:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a full pentesting replacement&lt;/li&gt;
&lt;li&gt;an enterprise security suite&lt;/li&gt;
&lt;li&gt;something that magically makes your app “secure forever”&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Launch &amp;amp; feedback&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I launched SecureNow today, and I’m genuinely looking for feedback — not hype.&lt;br&gt;
Things I’d really like to know:&lt;/p&gt;

&lt;p&gt;Is this actually useful?&lt;br&gt;
What checks would you expect from a tool like this?&lt;br&gt;
What would make you not trust it?&lt;br&gt;
Is the pricing off / too expensive for what it does?&lt;/p&gt;

&lt;p&gt;If you want to take a look:&lt;br&gt;
&lt;a href="https://www.securenow.dev" rel="noopener noreferrer"&gt;https://www.securenow.dev&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’m happy to answer questions, explain how things work, or hear why this is a terrible idea!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fg5t359itgp483n15vf5b.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fg5t359itgp483n15vf5b.png" alt="SecureNow Landing Page" width="800" height="468"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>security</category>
      <category>cybersecurity</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
