<?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: sitetoolsbox</title>
    <description>The latest articles on DEV Community by sitetoolsbox (@sitetoolsbox).</description>
    <link>https://dev.to/sitetoolsbox</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4186156%2F9e6d1490-2dc4-4d23-9f91-5e3367596a88.png</url>
      <title>DEV Community: sitetoolsbox</title>
      <link>https://dev.to/sitetoolsbox</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sitetoolsbox"/>
    <language>en</language>
    <item>
      <title>I got hacked, scraped, and copied. Here's why I still write pure Vanilla PHP</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Mon, 16 Nov 2026 12:09:12 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/i-got-hacked-scraped-and-copied-heres-why-i-still-write-pure-vanilla-php-3o4d</link>
      <guid>https://dev.to/sitetoolsbox/i-got-hacked-scraped-and-copied-heres-why-i-still-write-pure-vanilla-php-3o4d</guid>
      <description>&lt;p&gt;Epilogue: Why I Keep Walking&lt;/p&gt;

&lt;p&gt;I'm not a genius. I have no framework, no team, no capital. All I have is "not hiding"—getting hit and saying it publicly, making mistakes and admitting it publicly.&lt;/p&gt;

&lt;p&gt;I'm still updating. One person carrying everything: backend, frontend, ops, product, content, SEO, customer support, and promotion. I'm not good at everything; I have to be good at everything.&lt;/p&gt;

&lt;p&gt;If you want to see what a single developer with zero frameworks can build, or if you just want to use 20+ free, ad-free webmaster tools, come check out my site: &lt;a href="https://sitetoolsbox.com" rel="noopener noreferrer"&gt;https://sitetoolsbox.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'm still walking. Slow? Maybe. But I'm still walking.&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fb68rrv9m7bucueniht45.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fb68rrv9m7bucueniht45.png" alt=" " width="800" height="478"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Title: Is the era of independent developers over? My journey of building a site with pure PHP.</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Mon, 16 Nov 2026 06:50:10 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/title-is-the-era-of-independent-developers-over-my-journey-of-building-a-site-with-pure-php-cko</link>
      <guid>https://dev.to/sitetoolsbox/title-is-the-era-of-independent-developers-over-my-journey-of-building-a-site-with-pure-php-cko</guid>
      <description>&lt;p&gt;I've been asking myself this question a lot lately: &lt;em&gt;Is there still a way out for independent developers?&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Over the past few weeks, I've been burning the midnight oil. I decided to build my own directory and toolset entirely from scratch. No Laravel, no Symfony, no React, no heavy frameworks. Just &lt;strong&gt;pure, vanilla PHP&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It was a brutal but incredibly fulfilling process. I built &lt;strong&gt;20+ free online tools&lt;/strong&gt; (DNS lookups, WHOIS, HTTP status checkers, etc.) and launched the site. &lt;/p&gt;

&lt;p&gt;But the journey was far from smooth.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Spam Attacks
&lt;/h3&gt;

&lt;p&gt;About two weeks after launch, I almost got scared off the internet. My submission form was hit by bots. Hundreds of garbage links, fake crypto sites, and pure spam flooded my database. &lt;/p&gt;

&lt;p&gt;I didn't give up. I fought back. I patched the vulnerabilities, rewrote my database logic, and built my own anti-spam defenses (Rate limiting, HoneyPots, IP blocking). I got hit twice, and I survived both times.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Hardest Decision: Adding Google Login
&lt;/h3&gt;

&lt;p&gt;Even with all my defenses, the spam was still slipping through. I made a tough choice: I implemented Google OAuth. &lt;/p&gt;

&lt;p&gt;To prove they are real humans and to stop low-quality, automated submissions, users must now log in with a Google account to submit a site. &lt;strong&gt;The result? The spam literally dropped to zero overnight.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;But it made me think deeply.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Independent Developer's Dilemma
&lt;/h3&gt;

&lt;p&gt;I wanted to build a site that was:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; &lt;strong&gt;Completely free.&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Zero annoying pop-up ads.&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;No forced registration just to use the tools.&lt;/strong&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;But the reality is harsh. If you have no pop-ups and no registration walls, you get absolutely hammered by bots. &lt;/p&gt;

&lt;p&gt;Building this with pure PHP from scratch has been one of the hardest things I've ever done. Every time I fix a bug, another one pops up. &lt;/p&gt;

&lt;p&gt;So, I'm standing at a crossroads. As an independent developer, &lt;strong&gt;does this road still lead anywhere?&lt;/strong&gt; Is it still worth it to build things purely from the ground up, without relying on frameworks, just to give users a clean experience?&lt;/p&gt;

&lt;p&gt;I don't have the answer yet. But I'm still here, and the site is still running.&lt;/p&gt;

&lt;p&gt;If you're a fellow developer, I'd love to hear your thoughts. Have you ever felt this kind of framework fatigue? How do you deal with spam attacks on your side projects?&lt;/p&gt;




&lt;p&gt;*(Note: If you want to see what I've built and verify that pure PHP still works, you can check out my free tools here: &lt;a href="https://sitetoolsbox.com" rel="noopener noreferrer"&gt;https://sitetoolsbox.com&lt;/a&gt; All 20+ tools are completely free, no registration required to use them. Let's keep the web a clean place.)&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fknsh2iqdjtfcexxoms1f.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fknsh2iqdjtfcexxoms1f.png" alt=" " width="800" height="478"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>php</category>
      <category>indiehacker</category>
      <category>buildinpublic</category>
    </item>
    <item>
      <title>Where is the Way Out for Solo Webmasters? A Brutal Truth About Building 20 Tools</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Wed, 11 Nov 2026 01:04:51 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/where-is-the-way-out-for-solo-webmasters-a-brutal-truth-about-building-20-tools-5c3n</link>
      <guid>https://dev.to/sitetoolsbox/where-is-the-way-out-for-solo-webmasters-a-brutal-truth-about-building-20-tools-5c3n</guid>
      <description>&lt;p&gt;&lt;strong&gt;Where is the way out for independent webmasters?&lt;/strong&gt; When you start building your own platform from zero, the initial excitement quickly turns into a test of endurance. Every indie hacker knows the rush of hitting "Publish." You spend weeks staring at a blinking cursor, designing UI, and writing backend logic. When the site finally goes live with 20+ fully functional online tools, you feel like a god. You've built something out of nothing.&lt;/p&gt;

&lt;p&gt;But then, reality hits. And it hits hard.&lt;/p&gt;

&lt;h3&gt;The Illusion of "Build It and They Will Come"&lt;/h3&gt;

&lt;p&gt;When you are a solopreneur, you wear every hat: developer, designer, QA, and marketer. Launching 20 tools felt like a massive milestone. I thought the hard part was over. I spent my days tweaking the UI and writing SEO articles, waiting for the organic traffic to roll in.&lt;/p&gt;

&lt;p&gt;It didn't take long to realize that building the tools is only 20% of the journey. The remaining 80% is a brutal war of attrition.&lt;/p&gt;

&lt;h3&gt;The Wake-Up Call: When Your Server Gets Hit&lt;/h3&gt;

&lt;p&gt;The real turning point came when my server was suddenly flooded with malicious requests. Some script kiddie or an automated botnet found my API endpoints and decided to use my platform as a punching bag. The server didn't just slow down; it completely crashed.&lt;/p&gt;

&lt;p&gt;As a solo founder, there is no "IT department" to call. You can't just open a support ticket and go to sleep. I found myself at 3:00 AM, staring at Nginx error logs, trying to find the holes in my own code.&lt;/p&gt;

&lt;h3&gt;The Energy Depletion Phase&lt;/h3&gt;

&lt;p&gt;Over the next few days, I conducted a full-scale security audit. I dug into the code and found over 10 critical vulnerabilities—from open redirects and SSRF risks to missing CSRF tokens and API abuse flaws.&lt;/p&gt;

&lt;p&gt;Fixing them wasn't just about writing code. It was an exhausting mental drain. By the time I patched the last vulnerability and hardened the API rate-limiting logic, I realized a harsh truth: &lt;strong&gt;As an independent developer, your energy is not infinite, and your time is your most expensive asset.&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;The Real Way Out: Stop Reinventing the Wheel&lt;/h3&gt;

&lt;p&gt;This painful experience led to a massive realization. Since building, operating, and defending against malicious bots already takes up so much energy, why waste time building everything from scratch?&lt;/p&gt;

&lt;p&gt;This is exactly why I built &lt;a href="https://sitetoolsbox.com" rel="noopener noreferrer"&gt;&lt;strong&gt;Site Tools Box&lt;/strong&gt;&lt;/a&gt;—a curated directory of online tools designed specifically for webmasters and indie hackers. I turned the pain points I experienced into a clean, secure toolkit for you.&lt;/p&gt;

&lt;ul&gt;
    &lt;li&gt;
&lt;strong&gt;Security First:&lt;/strong&gt; Need to check DNS records, HTTP status codes, dead links, or domain availability? Every tool on our platform is strictly hardened and rate-limited, so you don't have to worry about API abuse.&lt;/li&gt;
    &lt;li&gt;
&lt;strong&gt;Zero Friction:&lt;/strong&gt; No forced sign-ups, no intrusive pop-up ads. Just lightning-fast tools because I know how valuable your time is.&lt;/li&gt;
    &lt;li&gt;
&lt;strong&gt;Built for Makers:&lt;/strong&gt; If you just launched your own product, you can submit it to our directory. We'll scan it for dead links and help you get discovered by search engines and real users.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Don't let server crashes and security vulnerabilities ruin your hard work. Leave the tedious checks to us, and keep your energy focused on your core business.&lt;/p&gt;

&lt;p&gt;``&lt;/p&gt;

&lt;p&gt;What is the biggest unexpected challenge you've faced while building your own project? Let me know in the comments, or go ahead and try our latest &lt;a href="https://sitetoolsbox.com" rel="noopener noreferrer"&gt;&lt;strong&gt;free online tools&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>security</category>
      <category>solopreneur</category>
      <category>devops</category>
    </item>
    <item>
      <title>How a Malicious Bot Attack Forced Me to Rebuild My Webmaster Tools on Edge Computing</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Mon, 09 Nov 2026 05:42:21 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/how-a-malicious-bot-attack-forced-me-to-rebuild-my-webmaster-tools-on-edge-computing-2n55</link>
      <guid>https://dev.to/sitetoolsbox/how-a-malicious-bot-attack-forced-me-to-rebuild-my-webmaster-tools-on-edge-computing-2n55</guid>
      <description>&lt;p&gt;Hey DEV community! 👋&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fo2zclvl89xazjtmnp5dx.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fo2zclvl89xazjtmnp5dx.png" alt=" " width="797" height="583"&gt;&lt;/a&gt;&lt;br&gt;
I’m the indie developer behind Site Tools Box, a free suite of 20+ webmaster tools (Dead Link Checker, WHOIS, UTM builder, etc.). We have a simple core philosophy: No intrusive ads, no forced sign-ups, just fast tools.&lt;/p&gt;

&lt;p&gt;But last week, I woke up to a nightmare. My server (a humble 2GB RAM machine) was screaming for mercy.&lt;/p&gt;

&lt;p&gt;Here is the story of how a malicious bot attack forced me to rethink my entire architecture, offload workloads to the Edge, and build a custom defense system. &lt;/p&gt;

&lt;p&gt;🚨 The Incident: The 0-Second Spam Attack&lt;/p&gt;

&lt;p&gt;I noticed a massive spike in my traffic logs. At first, I was excited—until I looked closer. &lt;/p&gt;

&lt;p&gt;Every single request was hitting my submit page (submit.php). The dwell time was exactly 0 seconds, and the exact same IP (66.227.112.166) was hammering my server every few seconds. It was a brute-force spam attack. &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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqk2uizcn6h1wbiud5dgk.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqk2uizcn6h1wbiud5dgk.png" alt=" " width="800" height="641"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Because my site is built with Vanilla PHP (no heavy frameworks), the server was trying to process every single request, query the database for the "Trending Tools" sidebar, and render the page. My memory limit was hitting the ceiling. I had to act fast.&lt;/p&gt;

&lt;p&gt;🛡️ Defense Mechanism 1: The PHP IP Blacklist&lt;/p&gt;

&lt;p&gt;I didn't want to mess with complex Nginx configurations or paid firewalls. I wanted a lightweight solution. So, I built a custom IP blacklist system.&lt;/p&gt;

&lt;p&gt;I hooked a function into my global functions.php file. Before any database query or page rendering happens, it checks a local JSON file:&lt;/p&gt;

&lt;p&gt;// Instant IP Blocking System&lt;br&gt;
function stb_check_ip_block() {&lt;br&gt;
    $ip = getClientIp(); // Handles Cloudflare real IP&lt;br&gt;
    $blockFile = &lt;strong&gt;DIR&lt;/strong&gt; . '/../data/blocked_ips.json';&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;if (file_exists($blockFile)) {
    $blocked = json_decode(file_get_contents($blockFile), true);
    if (is_array($blocked) &amp;amp;&amp;amp; in_array($ip, $blocked)) {
        header('HTTP/1.1 403 Forbidden');
        die('Your IP has been blocked by the administrator.');
    }
}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;}&lt;br&gt;
stb_check_ip_block();&lt;/p&gt;

&lt;p&gt;Now, I have a simple admin dashboard where I can paste an IP, click "Block", and they are instantly denied access at the very first layer. The bot is met with a cold 403 Forbidden.&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5xe4ocf0j8uiswuvfyyo.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5xe4ocf0j8uiswuvfyyo.png" alt=" " width="800" height="625"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🚀 Defense Mechanism 2: Moving the Heavy Lifting to the Edge&lt;/p&gt;

&lt;p&gt;The attack made me realize something: my server should not be doing heavy network requests. &lt;/p&gt;

&lt;p&gt;My most popular tool is the Dead Link Checker. Originally, a user would input a URL, my PHP server would scrape the page, find up to 300 links, and then curl each one to check its HTTP status. &lt;/p&gt;

&lt;p&gt;If 10 users did this at once, my server was making 3,000 concurrent requests. That’s a DDoS on my own server!&lt;/p&gt;

&lt;p&gt;So, I moved the heavy lifting to Cloudflare Workers.&lt;/p&gt;

&lt;p&gt;Now, my PHP server only scrapes the initial HTML (a single request). The frontend then sends the extracted links to a Cloudflare Worker via fetch().&lt;/p&gt;

&lt;p&gt;// Frontend Edge Request (Simplified)&lt;br&gt;
fetch('&lt;a href="https://my-worker.workers.dev/?url=" rel="noopener noreferrer"&gt;https://my-worker.workers.dev/?url=&lt;/a&gt;' + encodeURIComponent(link))&lt;br&gt;
  .then(res =&amp;gt; res.json())&lt;br&gt;
  .then(data =&amp;gt; {&lt;br&gt;
      // Worker returns status: 200 or status: 404&lt;br&gt;
      updateUI(link, data.status);&lt;br&gt;
  });&lt;/p&gt;

&lt;p&gt;My Worker script acts as a proxy, checking the links from Cloudflare's global network. &lt;/p&gt;

&lt;p&gt;The result? &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;My origin server no longer gets blacklisted by target websites.&lt;/li&gt;
&lt;li&gt;The scan is 10x faster because it's distributed across CF edge nodes.&lt;/li&gt;
&lt;li&gt;My 2GB RAM server usage dropped back to a peaceful 20%.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;💡 Why I'm Sharing This&lt;/p&gt;

&lt;p&gt;Building free tools for the community is incredibly rewarding, but it also makes you a target for bots. &lt;/p&gt;

&lt;p&gt;If you are running a lightweight PHP app, you don't need a massive enterprise firewall. A simple JSON blacklist and an Edge proxy can save your sanity (and your server bill).&lt;/p&gt;

&lt;p&gt;Our core promise at Site Tools Box hasn't changed: Free tools, no forced sign-ups, no BS. We are just making the infrastructure stronger so you can have a seamless experience.&lt;/p&gt;

&lt;p&gt;Have you guys ever dealt with bot spam? How did you handle it? Let me know in the comments! 👇&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>security</category>
      <category>php</category>
    </item>
    <item>
      <title>How I Got 200+ Visitors in 20 Days: Refactoring a Pure PHP Toolbox &amp; Adding Client-Side Security</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Sun, 08 Nov 2026 01:23:46 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/how-i-got-200-visitors-in-20-days-refactoring-a-pure-php-toolbox-adding-client-side-security-kb6</link>
      <guid>https://dev.to/sitetoolsbox/how-i-got-200-visitors-in-20-days-refactoring-a-pure-php-toolbox-adding-client-side-security-kb6</guid>
      <description>&lt;p&gt;Hey DEV community! 👋&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frxud8co7cino8vmrwgs7.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frxud8co7cino8vmrwgs7.png" alt=" " width="800" height="456"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;About three weeks ago, I launched Site Tools Box (&lt;a href="https://sitetoolsbox.com)%E2%80%94a" rel="noopener noreferrer"&gt;https://sitetoolsbox.com)—a&lt;/a&gt; free, no-login toolbox for webmasters. It started as a simple side project, but after a surprising burst of traffic from Hacker News (200+ unique visitors in 20 days), I realized I needed to seriously level up the architecture.&lt;/p&gt;

&lt;p&gt;Here is a breakdown of the latest technical updates, what I learned, and how I handled the "Zero-Login" challenge.&lt;/p&gt;

&lt;p&gt;🚀 1. The Hybrid Architecture: Speed &amp;amp; Privacy First&lt;br&gt;
When building a toolbox, you face a classic dilemma:&lt;/p&gt;

&lt;p&gt;Option A: Do everything on the server (slower, heavy server load, privacy risks).&lt;/p&gt;

&lt;p&gt;Option B: Do everything in the browser (faster, but limits complex queries).&lt;/p&gt;

&lt;p&gt;I chose a Hybrid Architecture.&lt;br&gt;
For tools like the JSON Formatter, the logic runs 100% in Vanilla JavaScript. Data never leaves the user's machine.&lt;br&gt;
But for Bulk Domain Lookups, browsers can't query WHOIS/RDAP directly due to CORS and protocol limits. So, I built a server-side endpoint using native PHP's curl_multi. This allows parallel querying of up to 30 domains instantly, bypassing the sequential delays of traditional WHOIS lookups.&lt;/p&gt;

&lt;p&gt;🔒 2. UI/UX Overhaul: Daily Domains&lt;br&gt;
I recently added a "Daily Domains" feature, curating unregistered .com and .ai domains. I used to display them in clunky cards, but users got visual fatigue quickly.&lt;/p&gt;

&lt;p&gt;I refactored the front-end to use a compact, single-row list grouped by date. It drastically reduced cognitive load. To handle the affiliate redirects cleanly, I pass the domain dynamically via URL parameters:&lt;br&gt;
&lt;a href="https://www.namecheap.com/domains/registration/results/?domain=%7Bdomain%7D" rel="noopener noreferrer"&gt;https://www.namecheap.com/domains/registration/results/?domain={domain}&lt;/a&gt;&lt;br&gt;
🛡️ 3. The "Zero-Login" Security Challenge (MD5, SHA, Bcrypt)&lt;br&gt;
Many users asked for a Password Generator. But as a developer, I know that generating a password is only half the battle—you need to hash it for storage.&lt;/p&gt;

&lt;p&gt;I upgraded the tool to include:&lt;/p&gt;

&lt;p&gt;MD5 / SHA-256 / Base64: Processed entirely via crypto-js in the browser.&lt;/p&gt;

&lt;p&gt;Bcrypt Hashing: This was the tricky part. Bcrypt requires high CPU work (the "salt rounds"). Running it in JS is possible, but heavy.&lt;/p&gt;

&lt;p&gt;The Tech Stack I used:&lt;/p&gt;

&lt;p&gt;🎨 4. Avoiding the "Ugly System Alert"&lt;br&gt;
One thing I hate about older web apps is the default alert() when you copy text. I wrote a tiny smooth-copy function that changes the button state to a green "✅ Copied!" and reverts after 1.5 seconds. Small details like this make a tool feel like a modern SaaS.&lt;/p&gt;

&lt;p&gt;🚀 What's Next?&lt;br&gt;
I'm currently focusing on SEO optimization and trying to get the tool indexed by more search engines. The recent jump in traffic from Japan (thanks to a tech media mention) has also motivated me to keep the UI language-neutral and fast.&lt;/p&gt;

&lt;p&gt;If you want to check it out or give me some feedback on the architecture, here is the link:&lt;br&gt;
Live Tool: &lt;a href="https://sitetoolsbox.com" rel="noopener noreferrer"&gt;https://sitetoolsbox.com&lt;/a&gt;&lt;br&gt;
GitHub: &lt;a href="https://github.com/kagouhui/site-tools-box" rel="noopener noreferrer"&gt;https://github.com/kagouhui/site-tools-box&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Thanks for reading! Happy coding! 💻&lt;/p&gt;

</description>
      <category>php</category>
      <category>javascript</category>
      <category>showdev</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How I Built a Custom Anti-Spam Rate Limiter for My PHP Site (No Cloudflare</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Thu, 05 Nov 2026 04:51:46 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/how-i-built-a-custom-anti-spam-rate-limiter-for-my-php-site-no-cloudflare-5a5d</link>
      <guid>https://dev.to/sitetoolsbox/how-i-built-a-custom-anti-spam-rate-limiter-for-my-php-site-no-cloudflare-5a5d</guid>
      <description>&lt;p&gt;If you run a free directory, the bots will find you. Within 48 hours of launching my free toolbox, I was getting hammered by automated scripts.&lt;/p&gt;

&lt;p&gt;I decided to ditch heavy WAF rules and build a custom rate limiter using pure vanilla PHP 8 with flat JSON files. No Redis, no database overhead.&lt;/p&gt;

&lt;p&gt;Here is how it works in 3 layers:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;The Honeypot &amp;amp; Time Check&lt;br&gt;
I added a hidden input field (bots fill it, humans don't). If filled, instant ban. I also record page load time. If a user submits in under 5 seconds, they are a bot.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Flat-File IP Rate Limiting&lt;br&gt;
Instead of querying the database on every attempt, I store IP timestamps in a JSON file (ip_limits.json). If an IP submits more than 3 times in 24 hours, I block them before any SQL runs.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The Server-Side Math CAPTCHA&lt;br&gt;
I generate two random numbers in a PHP session and ask the user to solve it (e.g., "What is 4 + 7?"). Scripts hate dynamic math.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The Result:&lt;br&gt;
Spam submissions dropped to absolute zero. Real users don't notice a thing. A few lines of vanilla PHP saved me hours of headaches.&lt;/p&gt;

&lt;p&gt;I'm currently building Site Tools Box, a free ad-free platform with 20+ developer tools and an AI Text Humanizer. You can see this anti-spam system in action here:&lt;br&gt;
&lt;a href="https://dev.tourl"&gt;👉 sitetoolsbox.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Have you ever fought a bot war on your own site? Let me know!&lt;/p&gt;

</description>
      <category>php</category>
      <category>webdev</category>
      <category>security</category>
      <category>showdev</category>
    </item>
    <item>
      <title>I built a free AI text humanizer with dual-engine fallback. Need some brutal feedback on the output.</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Wed, 04 Nov 2026 00:19:55 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/building-a-resilient-ai-text-humanizer-with-dual-engine-fallback-php-openrouter-2b1</link>
      <guid>https://dev.to/sitetoolsbox/building-a-resilient-ai-text-humanizer-with-dual-engine-fallback-php-openrouter-2b1</guid>
      <description>&lt;p&gt;Hey everyone,&lt;/p&gt;

&lt;p&gt;I got tired of "free" AI tools that actually charge you after 200 words. So I built my own over the weekend. It's a dual-engine setup (OpenRouter + SiliconFlow) written in pure PHP so it shouldn't crash when the API gets rate-limited.&lt;/p&gt;

&lt;p&gt;I also added a strict daily limit (5 uses per IP) because a botnet attacked my endpoint 50 times right after I launched it.&lt;/p&gt;

&lt;p&gt;I bundled it with 20+ other webmaster tools (WHOIS, DNS, JSON, etc). I'm mainly looking for feedback on the humanizer's output—does it actually sound natural to you?&lt;/p&gt;

&lt;p&gt;If you want to test it out, just type "sitetoolsbox.com" into your browser, the humanizer is in the AI section.&lt;/p&gt;

&lt;p&gt;What's the biggest pain point you usually hit with AI detectors? Would love to know what to improve.&lt;/p&gt;

</description>
      <category>php</category>
      <category>ai</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
    <item>
      <title>The Silent Killer of Uptime: Why You Must Master DNS Lookups</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Tue, 03 Nov 2026 00:33:04 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/the-silent-killer-of-uptime-why-you-must-master-dns-lookups-b7f</link>
      <guid>https://dev.to/sitetoolsbox/the-silent-killer-of-uptime-why-you-must-master-dns-lookups-b7f</guid>
      <description>&lt;p&gt;If you manage servers, deploy microservices, or just run a WordPress site, you've probably experienced it: A sudden, unexplainable outage. The server is running. The CPU is at 10%. The firewall is open. Yet, users are reporting that your site is completely unreachable.&lt;/p&gt;

&lt;p&gt;Nine times out of ten, the problem isn't your code. It's the invisible routing layer of the internet: &lt;strong&gt;DNS&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Most developers treat DNS as a "set it and forget it" configuration—a one-time A record update in their domain registrar. But DNS is incredibly fragile. Here is why you need to actively monitor it, and how to diagnose it in seconds.&lt;/p&gt;

&lt;h3&gt;1. The CNAME Chain Reaction&lt;/h3&gt;

&lt;p&gt;Many of us use CNAME records to point subdomains to third-party services (like an AWS Load Balancer, a Shopify store, or a Mailchimp server). The danger here is the "chain." If that upstream provider updates their IP address and breaks the chain, your subdomain goes dark.&lt;/p&gt;

&lt;p&gt;You can't just `ping` the domain; you need to query the exact record type. Our free &lt;strong&gt;&lt;a href="https://sitetoolsbox.com/tool.php?slug=dns" rel="noopener noreferrer"&gt;DNS Lookup Tool&lt;/a&gt;&lt;/strong&gt; allows you to instantly query the CNAME and trace where it's pointing. If it resolves to an IP that you don't recognize, you've found your culprit.&lt;/p&gt;

&lt;h3&gt;2. The "Propagation is Slow" Excuse&lt;/h3&gt;

&lt;p&gt;You changed your A record 3 hours ago, but half your users are still hitting the old server. You might think it's just "normal propagation." But if you are using Cloudflare or AWS Route 53, updates should be near-instant.&lt;/p&gt;

&lt;p&gt;If you suspect slow propagation, run a query against the specific nameservers using our tool. You can check the &lt;strong&gt;NS records&lt;/strong&gt; and the &lt;strong&gt;SOA records&lt;/strong&gt; to see exactly what the authoritative name server is broadcasting. It gives you the hard truth before you blame the ISP.&lt;/p&gt;

&lt;h3&gt;3. The Silent Email Killer (MX &amp;amp; SPF)&lt;/h3&gt;

&lt;p&gt;Your website loads fine, but your contact form emails are bouncing, or customers aren't receiving password resets. This is a classic MX (Mail Exchanger) misconfiguration. Or worse, your TXT records (SPF/DKIM) are missing, causing Google and Microsoft to instantly trash your transactional emails.&lt;/p&gt;

&lt;p&gt;A DNS Lookup isn't just for web traffic. Querying the &lt;strong&gt;MX&lt;/strong&gt; and &lt;strong&gt;TXT&lt;/strong&gt; records ensures your mail routing and domain verification are bulletproof.&lt;/p&gt;

&lt;h3&gt;How to Diagnose Any DNS Issue in 5 Seconds&lt;/h3&gt;

&lt;p&gt;Stop opening a terminal and typing `nslookup` or `dig` blindly. It's clunky, and if you're on a restricted network or VPN, the results might be cached locally and give you a false reading.&lt;/p&gt;

&lt;p&gt;Use our web-based &lt;strong&gt;&lt;a href="https://sitetoolsbox.com/tool.php?slug=dns" rel="noopener noreferrer"&gt;DNS Lookup Tool&lt;/a&gt;&lt;/strong&gt;. It queries from our high-availability infrastructure, meaning you get a clean, uncached, real-world view of your DNS records.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Features you can use right now:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
    &lt;li&gt;Check A and AAAA records to verify dual-stack (IPv4/IPv6) configurations.&lt;/li&gt;
    &lt;li&gt;Verify CNAME aliases to prevent routing loops.&lt;/li&gt;
    &lt;li&gt;Validate TXT records for SPF domain verification.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Whether you are a sysadmin fighting a 2 AM outage or a webmaster setting up a new domain, DNS is your first line of defense. Bookmark the tool, and save yourself hours of hair-pulling.&lt;/p&gt;

&lt;p&gt;👉 &lt;strong&gt;&lt;a href="https://sitetoolsbox.com/tool.php?slug=dns" rel="noopener noreferrer"&gt;Run a Free DNS Lookup Now →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>dnslookup</category>
      <category>webdev</category>
      <category>sysadmin</category>
      <category>networktroubleshooting</category>
    </item>
    <item>
      <title>Stop Using Slow APIs: The Right Way to Bulk Check HTTP Statuses (50+ URLs in Seconds)</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Sat, 31 Oct 2026 06:03:17 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/stop-using-slow-apis-the-right-way-to-bulk-check-http-statuses-50-urls-in-seconds-b62</link>
      <guid>https://dev.to/sitetoolsbox/stop-using-slow-apis-the-right-way-to-bulk-check-http-statuses-50-urls-in-seconds-b62</guid>
      <description>&lt;p&gt;Last week, I found myself staring at a dead-links report for an old client project. Over 300 pages. I needed to know which URLs were returning 404s, which ones were silently redirecting, and which ones had just given up entirely.&lt;/p&gt;

&lt;p&gt;My first instinct was to write a quick loop in Node.js using &lt;code&gt;fetch&lt;/code&gt;. &lt;/p&gt;

&lt;p&gt;I hit two massive walls immediately:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The Rate Limit / IP Ban wall:&lt;/strong&gt; After about 15 requests, the target servers started dropping my connection.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Timeout wall:&lt;/strong&gt; My script hung for 5 minutes because three random URLs just never responded.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you've ever tried to bulk check HTTP statuses at scale, you know the pain. So, let me save you a few hours of frustration.&lt;/p&gt;

&lt;p&gt;Here is the breakdown of how this &lt;em&gt;should&lt;/em&gt; work, and a free tool I started using to bypass the headache entirely.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Naive Approach (And Why It Fails)
&lt;/h3&gt;

&lt;p&gt;Here’s how most of us start writing a bulk HTTP checker:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
javascript
// DON'T DO THIS FOR BULK CHECKS
async function checkUrls(urls) {
  for (const url of urls) {
    try {
      const res = await fetch(url, { method: 'HEAD' });
      console.log(url, res.status);
    } catch (e) {
      console.log(url, 'Error');
    }
  }
}

This is a disaster for a few reasons:

HEAD isn't always supported: Some servers block HEAD requests and only return a valid 200 for GET.

No Concurrency Control: If you use Promise.all(), you’ll fire 50 requests at once and your IP will get blocked by Cloudflare instantly.

No Timeouts: A single hanging URL will block your entire script.

The "Developer" Way to Fix It
To do this properly in a script, you need to implement:

Connection Pooling / Semaphores (to limit concurrency to ~5 requests at a time).

Custom AbortControllers (to kill requests after 5 seconds).

User-Agent spoofing (so it looks like a real browser).

It’s a fun technical exercise, but when you’re on a deadline and just need the data, writing this whole infrastructure is a waste of time.

The Alternative: Automate It Without the Code
When I realized I was spending more time debugging my scraper than actually auditing the site, I switched to using a bulk HTTP checker tool I found online.

I’ve been using Bulk HTTP Checker on Site Tools Box.

It’s a lightweight, backend-optimized tool that handles all the heavy lifting for you. You can paste up to 50 URLs, hit run, and it handles the concurrency, redirects, and timeouts instantly.

It returns a clean list of:

Status Codes (200, 301, 404, 500)

Redirect chains (where it actually goes)

Response times

And because it’s built for developers, it doesn't try to sell you a $29/month subscription for a simple check.

One Last Pro-Tip for SEO / Auditing
If you have a sitemap and want to find out which specific pages on your site are broken, you don't even need to copy-paste manually. Just use the Dead Link Checker on Site Tools Box. It scans a page, crawls the outgoing links, and highlights any broken ones in red. I used it to find 3 dead links in my footer that had been silently 404-ing for months.

Don't waste your weekends writing semaphores for a script you'll only use once. Optimize your workflow, and get back to writing actual code.

Have you ever accidentally DoS'd a server with a Promise.all() loop? Let me know in the comments. We've all been there.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>productivity</category>
      <category>nocode</category>
    </item>
    <item>
      <title>Why I Dumped GA4 to Build a 2KB Privacy-First Stats System (and Caught a Fake "Big Tech" Company)</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Fri, 30 Oct 2026 00:07:28 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/why-i-dumped-ga4-to-build-a-2kb-privacy-first-stats-system-and-caught-a-fake-big-tech-company-3fgm</link>
      <guid>https://dev.to/sitetoolsbox/why-i-dumped-ga4-to-build-a-2kb-privacy-first-stats-system-and-caught-a-fake-big-tech-company-3fgm</guid>
      <description>&lt;p&gt;When I launched my side project—a curated directory for webmaster and SEO tools—I did what everyone does: I slapped Google Analytics (GA4) on it. &lt;/p&gt;

&lt;p&gt;But within a week, I was frustrated. GA4 felt bloated, it added heavy JS files to my tiny server (2-core, 2GB RAM), and the "bot filtering" was practically non-existent. I was getting hundreds of "visits" a day, but my PayPal account remained empty.&lt;/p&gt;

&lt;p&gt;I realized I needed a brutal, no-nonsense way to see exactly &lt;em&gt;who&lt;/em&gt; was hitting my site.&lt;/p&gt;

&lt;p&gt;So, I deleted GA4 and built my own analytics system from scratch. Here is how it went, and the hilarious trap it helped me uncover.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Architecture: Keep It Dead Simple
&lt;/h2&gt;

&lt;p&gt;I didn't want to spin up a heavy MySQL database just for logging. I wanted something I could read with my own eyes.&lt;/p&gt;

&lt;p&gt;I decided to use &lt;strong&gt;JSONL (JSON Lines)&lt;/strong&gt; and a tiny PHP endpoint.&lt;/p&gt;

&lt;p&gt;Here is how the data flows:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A lightweight JS &lt;code&gt;fetch()&lt;/code&gt; on the main site sends a &lt;code&gt;POST&lt;/code&gt; request to my stats subdomain.&lt;/li&gt;
&lt;li&gt;The PHP API receives the data (URL, Referer, User-Agent, IP).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Core Logic:&lt;/strong&gt; The PHP script regex-matches the User-Agent against a list of known bot strings (&lt;code&gt;googlebot&lt;/code&gt;, &lt;code&gt;ahrefs&lt;/code&gt;, &lt;code&gt;python&lt;/code&gt;, &lt;code&gt;crawl&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;If it's a bot, it's flagged as &lt;code&gt;is_spider: 1&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The data is appended to a daily text file: &lt;code&gt;log_2026-10-30.jsonl&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Here is what a raw log entry looks like:&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
json
{"time":"15:41:56","ip":"43.128.87.232","country":"France","url":"/pay.php","ref":"","ua":"Mozilla/5.0 (Macintosh; Intel Mac OS X...)","is_spider":0}

The Moment It Paid Off: Catching the "Fake Big Tech"
Because I now have the raw IP and User-Agent, my dashboard separates the noise from the real people.

Yesterday, my stats showed a "Real Human" hitting my /pay.php page. I got excited—someone was actually looking to pay for my premium listing!

But then, I noticed something strange in the logs. A company called "Logipax" submitted their site. Their landing page was incredible. It claimed to be a top-tier passenger transport SaaS operating "Since 1995", complete with a London map background and enterprise pricing.

It looked like a massive, established European company. Why would they submit to a new, tiny directory?

Curiosity got the better of me. I pulled their IP from my JSONL log and ran a quick WHOIS lookup.

The result was hilarious.

The domain logipax.io was registered just 4 days ago.

They had built a highly polished UI, written fake enterprise copy, and spammed every directory on the web to build SEO backlinks. If I had been using GA4, I would have just seen a "session from the UK" and approved them without thinking.

(Insert your screenshot of the WHOIS lookup here)

The Takeaway for Indie Hackers
Building this tiny 2KB system changed how I view web traffic. It's no longer just a number on a chart; it's a real story.

GA4 is overkill for side projects. If you just want to know if real humans are visiting, build your own logger. It's a fun weekend project.

Bots are loud, humans are quiet. 70% of my daily traffic is just Ahrefs and Googlebot. Seeing this visually stopped me from stressing out over "zero traffic."

Data ownership is freedom. I can run custom SQL queries, filter by country, and spot fake traffic instantly, all without paying a monthly SaaS fee.

If you're building something small, don't be afraid to strip things down. The best stack is the one you actually understand.

(If you want to see the final result or find some cool dev tools, you can check out my project here: Site Tools Box.)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>webdev</category>
      <category>seo</category>
      <category>security</category>
      <category>showdev</category>
    </item>
    <item>
      <title>How I Built a Bulk Domain Availability Checker with RDAP and Automated Scoring</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Wed, 28 Oct 2026 02:23:31 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/how-i-built-a-bulk-domain-availability-checker-with-rdap-and-automated-scoring-32h4</link>
      <guid>https://dev.to/sitetoolsbox/how-i-built-a-bulk-domain-availability-checker-with-rdap-and-automated-scoring-32h4</guid>
      <description>&lt;p&gt;I recently found myself needing to buy a short, brandable domain for a side project. I spent hours typing names into GoDaddy, only to get frustrated by the slow interface and the constant upsells.&lt;/p&gt;

&lt;p&gt;As a developer, I thought: "Why not just query the RDAP registries directly and score the domains algorithmically?"&lt;/p&gt;

&lt;p&gt;So I built a free tool to do exactly that. Here is how it works and why RDAP is the future of domain checking.&lt;/p&gt;

&lt;p&gt;The Problem with Traditional WHOIS&lt;br&gt;
Most domain tools still use standard WHOIS (Port 43). It is plain text, rate-limits aggressively, and often gets blocked by registrars.&lt;/p&gt;

&lt;p&gt;RDAP (Registration Data Access Protocol) is the modern, ICANN-mandated replacement. It returns structured JSON and uses standard HTTPS status codes:&lt;/p&gt;

&lt;p&gt;200 OK = Domain is registered.&lt;/p&gt;

&lt;p&gt;404 Not Found = Domain is available.&lt;/p&gt;

&lt;p&gt;This makes it incredibly easy for developers to query concurrently without getting blocked.&lt;/p&gt;

&lt;p&gt;The Architecture&lt;br&gt;
I built a tool that lets you paste up to 50 domains (one per line). Instead of firing 50 requests at once and getting rate-limited, the backend processes them in small concurrent batches (using curl_multi in PHP).&lt;/p&gt;

&lt;p&gt;Here is what the result dashboard looks like:&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft0jqkssyzuoetmkzhfc8.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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ft0jqkssyzuoetmkzhfc8.png" alt=" " width="800" height="858"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The Domain Scoring Algorithm&lt;br&gt;
Just knowing if a domain is available isn't enough. You need to know if it's actually good.&lt;/p&gt;

&lt;p&gt;I wrote an algorithmic scoring system (0-100) that evaluates domains across 5 dimensions:&lt;/p&gt;

&lt;p&gt;Extension (TLD): .com, .ai, .io score highest.&lt;/p&gt;

&lt;p&gt;Length: Short names (4-5 letters) get exponential value.&lt;/p&gt;

&lt;p&gt;Pronounceability: It analyzes vowel-consonant patterns (CVCV) to ensure it's easy to say.&lt;/p&gt;

&lt;p&gt;Meaning: Checks against a built-in dictionary of common English words.&lt;/p&gt;

&lt;p&gt;Brand Fit: Looks for industry prefixes like AI, tech, or e-commerce.&lt;/p&gt;

&lt;p&gt;If a domain scores 80+, it's highlighted in red as a 🔥 High Value domain. You can copy all the high-value results to your clipboard with one click.&lt;/p&gt;

&lt;p&gt;Why I Made It Free (For Now)&lt;br&gt;
I'm currently offering single checks for free. Building this has taught me a lot about RDAP and concurrent API handling.&lt;/p&gt;

&lt;p&gt;If you want to try it out, you can check it here:&lt;br&gt;
👉 Site Tools Box - Domain Availability Check&lt;/p&gt;

&lt;p&gt;(Note: The bulk check feature is currently locked behind a Pro tier while I optimize the server load, but single checks are 100% free).&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>api</category>
      <category>nocode</category>
    </item>
    <item>
      <title>Iterating on a Domain Checker: Adding Timestamps, Sources, and IANA Bootstrap</title>
      <dc:creator>sitetoolsbox</dc:creator>
      <pubDate>Tue, 27 Oct 2026 03:20:23 +0000</pubDate>
      <link>https://dev.to/sitetoolsbox/iterating-on-a-domain-checker-adding-timestamps-sources-and-iana-bootstrap-591l</link>
      <guid>https://dev.to/sitetoolsbox/iterating-on-a-domain-checker-adding-timestamps-sources-and-iana-bootstrap-591l</guid>
      <description>&lt;p&gt;A few days ago, I wrote a post about how I built a bulk domain availability checker using PHP and RDAP (instead of the traditional WHOIS protocol) over at &lt;a href="https://sitetoolsbox.com" rel="noopener noreferrer"&gt;Site Tools Box&lt;/a&gt;. &lt;/p&gt;

&lt;p&gt;To my surprise, the post got some fantastic technical feedback from the community. One comment from a developer named Furqan completely nailed some of the pain points I was already struggling with in production.&lt;/p&gt;

&lt;p&gt;Here are the three brilliant suggestions he made, and how I'm currently implementing them to make the tool more reliable.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. The "Premium Domain" Illusion: Why a 404 is Just a Hint
&lt;/h2&gt;

&lt;p&gt;In my previous post, I mentioned that querying RDAP returns a &lt;code&gt;404 Not Found&lt;/code&gt; if a domain is available, and &lt;code&gt;200 OK&lt;/code&gt; if it's registered. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The problem?&lt;/strong&gt; Premium and reserved domains. Sometimes, a registry will return a &lt;code&gt;404&lt;/code&gt; because it's technically unregistered, but it's actually a premium name that requires a 5-figure price tag at the registrar.&lt;/p&gt;

&lt;p&gt;Furqan's suggestion: &lt;strong&gt;Flag 404s as "Likely Available" instead of a hard "Yes".&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This is a brilliant UX change. I'm now updating the frontend to display a "Likely Available" badge with a tooltip explaining that premium domains can sometimes show as available but are locked behind a premium price wall.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Transparency: Adding "Last Checked" Timestamps and Sources
&lt;/h2&gt;

&lt;p&gt;Right now, when you check a domain on &lt;a href="https://sitetoolsbox.com/tool.php?slug=domain_check" rel="noopener noreferrer"&gt;Site Tools Box&lt;/a&gt;, you get the result, but you don't know &lt;em&gt;when&lt;/em&gt; it was checked or &lt;em&gt;where&lt;/em&gt; the data came from.&lt;/p&gt;

&lt;p&gt;Furqan suggested adding a "last checked" timestamp and the source (RDAP vs. WHOIS). &lt;/p&gt;

&lt;p&gt;This is crucial for debugging. When doing bulk checks of 100+ domains, network timeouts happen. By displaying the exact timestamp and the specific RDAP server endpoint used (e.g., &lt;code&gt;rdap.verisign.com&lt;/code&gt;), users can immediately tell if a result is stale or if the query failed.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Ditching the Hardcoded Map for IANA Bootstrap
&lt;/h2&gt;

&lt;p&gt;In my original PHP code, I had a massive &lt;code&gt;switch&lt;/code&gt; statement and array mapping TLDs to their respective RDAP servers (e.g., &lt;code&gt;.com&lt;/code&gt; -&amp;gt; Verisign, &lt;code&gt;.io&lt;/code&gt; -&amp;gt; Identity Digital). &lt;/p&gt;

&lt;p&gt;Furqan pointed out the obvious scaling issue: &lt;strong&gt;This hardcoded map is a nightmare to maintain.&lt;/strong&gt; What happens when a new TLD like &lt;code&gt;.xyz&lt;/code&gt; or &lt;code&gt;.ai&lt;/code&gt; changes its registry?&lt;/p&gt;

&lt;p&gt;His solution: &lt;strong&gt;Use IANA's Bootstrap file.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;IANA provides a public JSON file (&lt;code&gt;https://data.iana.org/rdap/dns.json&lt;/code&gt;) that automatically maps every TLD to its current RDAP endpoint. I'm currently rewriting my backend to fetch this file, cache it locally, and dynamically route queries. This means the tool will automatically support new TLDs without me lifting a finger.&lt;/p&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
php
// Pseudo-code for the new dynamic approach
$bootstrapUrl = 'https://data.iana.org/rdap/dns.json';
$bootstrapData = json_decode(file_get_contents($bootstrapUrl), true);

// Dynamically find the endpoint for .com
foreach ($bootstrapData['services'] as $service) {
    if (in_array('com', $service[0])) {
        $endpoint = $service[1][0];
        break;
    }
}



The Takeaway: Build in Public, Iterate Fast
This whole experience has been a masterclass in building in public. The feedback from the dev community is invaluable. What you think is a solid MVP might have fatal edge cases in the real world.

If you want to see the updated tool (and test the new features as they roll out), you can check it out here: Free Domain Availability Checker.

Have you ever built a tool that had to handle messy edge cases like premium domains or dynamic TLD routing? Let me know in the comments!
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>php</category>
      <category>webdev</category>
      <category>seo</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
