<?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: dnlcodes23</title>
    <description>The latest articles on DEV Community by dnlcodes23 (@dnlcodes23).</description>
    <link>https://dev.to/dnlcodes23</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%2F3937351%2F42ec0c04-a351-4264-acbd-939c7cd7d7e5.png</url>
      <title>DEV Community: dnlcodes23</title>
      <link>https://dev.to/dnlcodes23</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dnlcodes23"/>
    <language>en</language>
    <item>
      <title>I built a simple Email Cleaner tool — looking for feedback</title>
      <dc:creator>dnlcodes23</dc:creator>
      <pubDate>Mon, 18 May 2026 06:30:46 +0000</pubDate>
      <link>https://dev.to/dnlcodes23/i-built-a-simple-email-cleaner-tool-looking-for-feedback-118h</link>
      <guid>https://dev.to/dnlcodes23/i-built-a-simple-email-cleaner-tool-looking-for-feedback-118h</guid>
      <description>&lt;p&gt;I’ve been learning and experimenting, so I decided to build a small tool called Email Cleaner.&lt;br&gt;
It’s a simple project, but it helped me practice validation logic, error handling, and working with external checks.&lt;/p&gt;

&lt;p&gt;I’m sharing it here because I’d love to get feedback from more experienced developers.&lt;br&gt;
🧹 What the tool does&lt;br&gt;
The Email Cleaner scans a list of email addresses and removes or flags:&lt;/p&gt;

&lt;p&gt;invalid or malformed emails&lt;br&gt;
non‑existent domains&lt;br&gt;
disposable / temporary emails&lt;br&gt;
spam‑trap domains&lt;br&gt;
role‑based addresses like info@, admin@, support@&lt;/p&gt;

&lt;p&gt;The goal is to improve deliverability and reduce bounce rates.&lt;br&gt;
🛠️ How it works&lt;br&gt;
The tool uses a combination of:&lt;/p&gt;

&lt;p&gt;syntax validation&lt;br&gt;
domain (MX) checks&lt;br&gt;
mailbox‑level verification&lt;br&gt;
simple filtering rules&lt;/p&gt;

&lt;p&gt;I tried to keep the code clean and readable so it’s easy to understand for beginners&lt;br&gt;
Here’s the project if you want to check it out:&lt;br&gt;
👉 &lt;a href="https://github.com/dnlcodes23/email-cleaner.git" rel="noopener noreferrer"&gt;https://github.com/dnlcodes23/email-cleaner.git&lt;/a&gt;&lt;br&gt;
🙏 What I’d love feedback on&lt;br&gt;
I’m still learning, so any advice is welcome.&lt;br&gt;
Specifically, I’d appreciate thoughts on:&lt;/p&gt;

&lt;p&gt;code structure&lt;br&gt;
performance&lt;br&gt;
validation accuracy&lt;br&gt;
naming / organization&lt;br&gt;
ideas for new features&lt;/p&gt;

&lt;p&gt;Even small suggestions help a lot.&lt;br&gt;
💬 Thanks for reading&lt;br&gt;
If you take a moment to look at the project, thank you — I really appreciate it.&lt;br&gt;
I’m trying to improve step by step, and feedback from the community means a lot.&lt;/p&gt;

&lt;p&gt;If you want, I can also write:&lt;br&gt;
a shorter Dev.to version&lt;br&gt;
a more technical version&lt;br&gt;
a more beginner‑friendly version&lt;br&gt;
a version with screenshots&lt;br&gt;
Just tell me what style you want.&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>opensource</category>
      <category>api</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
