<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[TQ Nexus Blog]]></title><description><![CDATA[Practical guides on B2B lead generation, data scraping, email verification and cold email infrastructure by Tauqeer Ahmed, founder of TQ Nexus.]]></description><link>https://tqnexus.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6afac81666c9170c9a71d55a/a7eddf57-7edc-4d0c-8e0c-2086cb534604.png</url><title>TQ Nexus Blog</title><link>https://tqnexus.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 15:56:37 GMT</lastBuildDate><atom:link href="https://tqnexus.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[SPF, DKIM and DMARC Setup for Cold Email Domains]]></title><description><![CDATA[Learn how to set up SPF, DKIM and DMARC for cold email domains, test them with Gmail, and avoid the common DNS mistakes that send emails to spam.]]></description><link>https://tqnexus.hashnode.dev/spf-dkim-and-dmarc-setup-for-cold-email-domains</link><guid isPermaLink="true">https://tqnexus.hashnode.dev/spf-dkim-and-dmarc-setup-for-cold-email-domains</guid><category><![CDATA[email marketing]]></category><category><![CDATA[dns]]></category><category><![CDATA[cold email]]></category><category><![CDATA[email deliverability]]></category><category><![CDATA[B2B marketing]]></category><category><![CDATA[b2b]]></category><dc:creator><![CDATA[TQ Nexus LLC]]></dc:creator><pubDate>Thu, 19 Nov 2026 12:36:18 GMT</pubDate><content:encoded><![CDATA[<p>Before a cold email reaches anyone, the receiving server asks one question: is this sender who they claim to be? Three DNS records answer it: SPF, DKIM and DMARC. If they are missing or wrong, your emails go to spam or get rejected, and no amount of good copy fixes that.</p>
<p>This guide shows how to set up all three for a domain you use for cold outreach, in the order I do it, and how to check that they work before you send a single email.</p>
<h2>Why cold email domains need all three</h2>
<p>Since 2024, Google and Yahoo require authentication from bulk senders, and in practice every sender benefits from it. Even at low volume, a domain with no authentication looks suspicious to inbox providers. Cold outreach is already a high scrutiny activity, so you want every trust signal in place.</p>
<p>A quick note on setup: send cold email from separate domains, not your main company domain. If a cold domain gets damaged, your main domain and your normal business email stay safe.</p>
<h2>SPF: who is allowed to send</h2>
<p>SPF is a DNS TXT record that lists the servers allowed to send mail for your domain.</p>
<p>Example for a domain that sends through Google Workspace:</p>
<pre><code class="language-plaintext">Type: TXT
Host: @
Value: v=spf1 include:_spf.google.com ~all
</code></pre>
<p>Rules to remember:</p>
<ul>
<li>A domain can have only one SPF record. Two records break SPF completely.</li>
<li>If you send through more than one service, merge them into one record, for example <code>v=spf1 include:_spf.google.com include:otherservice.com ~all</code>.</li>
<li>SPF allows a maximum of 10 DNS lookups. Too many includes will make it fail.</li>
<li><code>~all</code> is a soft fail and <code>-all</code> is a hard fail. Most people start with <code>~all</code>.</li>
</ul>
<h2>DKIM: proof the email was not changed</h2>
<p>DKIM adds a digital signature to every email. Your mail provider gives you a public key, and you publish it in DNS.</p>
<ol>
<li>In your mail provider admin panel (for Google Workspace, this is under Gmail authentication), generate a DKIM key. Use the 2048 bit option if it is offered.</li>
<li>The panel shows a TXT host name, usually something like <code>google._domainkey</code>, and a long value starting with <code>v=DKIM1</code>.</li>
<li>Add that TXT record in your DNS exactly as shown.</li>
<li>Go back to the panel and click Start authentication.</li>
</ol>
<p>Copy the value carefully. A missing character is the most common reason DKIM fails.</p>
<h2>DMARC: what to do when checks fail</h2>
<p>DMARC tells receiving servers what to do if SPF and DKIM fail, and where to send reports. It is also a TXT record:</p>
<pre><code class="language-plaintext">Type: TXT
Host: _dmarc
Value: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
</code></pre>
<p>The policy has three levels:</p>
<ul>
<li><code>p=none</code>: monitor only, take no action. Start here.</li>
<li><code>p=quarantine</code>: failing emails go to spam.</li>
<li><code>p=reject</code>: failing emails are blocked.</li>
</ul>
<p>For a new cold domain I start with <code>p=none</code>, read the reports for a week or two to confirm everything passes, then move to <code>quarantine</code>. The important part is that the record exists and your mail passes alignment, which means the domain in the From address matches the domain that passed SPF or DKIM.</p>
<h2>Do not forget these extras</h2>
<ul>
<li><strong>Custom tracking domain.</strong> If your sending tool tracks opens or clicks, use your own tracking subdomain instead of a shared one. Shared tracking domains are used by many senders and can carry a bad reputation. Many senders now turn tracking off for the first emails.</li>
<li><strong>Reverse DNS and a valid MX.</strong> The domain should be able to receive mail, not only send it.</li>
<li><strong>One click unsubscribe and low spam complaints.</strong> Keep spam complaints well under 0.3 percent, and ideally far lower.</li>
</ul>
<h2>How to test before you send</h2>
<ol>
<li>Send a test email from the new mailbox to a Gmail address, open it, click the three dots and choose Show original. You should see SPF: PASS, DKIM: PASS and DMARC: PASS.</li>
<li>Use a free DNS checker to confirm there is only one SPF record and that the DKIM and DMARC records are visible.</li>
<li>Send test emails to a few different providers and check where they land.</li>
</ol>
<p>Only after all three pass should you start warming the mailbox. Warmup is a separate step, and skipping it is the next most common mistake after broken DNS.</p>
<h2>Common mistakes</h2>
<ul>
<li>Two SPF records on the same domain.</li>
<li>Setting up DNS on the wrong domain, for example the main domain instead of the sending domain.</li>
<li>Pasting DKIM keys with extra spaces or line breaks.</li>
<li>Starting with <code>p=reject</code> before confirming that everything passes.</li>
<li>Sending from a brand new domain at full volume on day one.</li>
</ul>
<h2>Want it done for you</h2>
<p>Setting up domains, mailboxes and DNS correctly takes time, and one small error can cost weeks of reputation. I build this setup for clients through my <a href="https://tqnexus.com/cold-email-infrastructure.php">cold email infrastructure service</a>, with domains, mailboxes, authentication and warmup ready before the first campaign. If you want the full outbound system on top, see my <a href="https://tqnexus.com/lead-generation-agency.php">lead generation agency</a> page.</p>
]]></content:encoded></item><item><title><![CDATA[How to Build a B2B Lead List From Scratch: Sources, Filters and Verification]]></title><description><![CDATA[A step by step guide to building a B2B lead list: define your ideal customer, find sources, collect and enrich data, then verify before you send.]]></description><link>https://tqnexus.hashnode.dev/how-to-build-a-b2b-lead-list-from-scratch-sources-filters-and-verification</link><guid isPermaLink="true">https://tqnexus.hashnode.dev/how-to-build-a-b2b-lead-list-from-scratch-sources-filters-and-verification</guid><category><![CDATA[lead generation]]></category><category><![CDATA[b2b]]></category><category><![CDATA[B2B marketing]]></category><category><![CDATA[cold email]]></category><category><![CDATA[data scraping]]></category><category><![CDATA[email marketing]]></category><dc:creator><![CDATA[TQ Nexus LLC]]></dc:creator><pubDate>Wed, 18 Nov 2026 10:08:40 GMT</pubDate><content:encoded><![CDATA[<p>A good B2B lead list is the base of every outbound campaign. If the list is wrong, the best email copy and the best sending setup will still fail. If the list is right, even a simple message can start real conversations.</p>
<p>This guide shows how to build a B2B lead list from scratch: how to define who you want, where to find them, how to collect and enrich the data, and how to clean it before you send anything.</p>
<h2>What a good B2B lead list looks like</h2>
<p>A useful lead list is not just a long list. Each row should meet four conditions:</p>
<ul>
<li><strong>Right company.</strong> It matches your ideal customer by industry, size and location.</li>
<li><strong>Right person.</strong> The contact has a job title that actually decides on or influences what you sell.</li>
<li><strong>Working email.</strong> The address exists and accepts mail.</li>
<li><strong>Fresh data.</strong> The person still works there and the company is still active.</li>
</ul>
<p>A list of 500 contacts that meets all four is worth more than a list of 5,000 that does not.</p>
<h2>Step 1: Define your ideal customer</h2>
<p>Before you collect anything, write down who you want to reach. Be specific:</p>
<ul>
<li>Industry or niche (for example, accounting firms, solar installers, SaaS startups)</li>
<li>Company size, by employees or revenue</li>
<li>Country or region</li>
<li>Job titles of the decision maker, such as founder, managing director or head of marketing</li>
<li>A reason they might need you now, such as hiring for a related role or opening a new location</li>
</ul>
<p>The narrower your definition, the easier it is to write a message that feels relevant to the reader.</p>
<h2>Step 2: Choose your data sources</h2>
<p>Good sources depend on your market. Common starting points include:</p>
<ul>
<li><strong>Business directories and listings.</strong> Maps listings and industry directories show company names, websites, addresses and phone numbers for local and regional businesses.</li>
<li><strong>Company websites.</strong> Team, about and contact pages often show names, job titles and sometimes email addresses.</li>
<li><strong>Industry associations and event pages.</strong> Member lists and speaker lists show active companies in a niche.</li>
<li><strong>Public registries.</strong> Company registries give legal names, locations and registration details.</li>
<li><strong>Job boards.</strong> A company hiring for a related role is often a strong buying signal.</li>
<li><strong>Data providers.</strong> Paid databases save time, but quality varies, so always verify what you buy.</li>
</ul>
<p>Always respect each site's terms of use and the law in your market, and avoid collecting data that sits behind a login or is not meant to be public.</p>
<h2>Step 3: Collect the data in a clean structure</h2>
<p>Decide the columns before you scrape or copy anything, so every source lands in the same format:</p>
<ul>
<li>Company name and website</li>
<li>Industry and location</li>
<li>Contact first name, last name and job title</li>
<li>Business email address</li>
<li>Source and date collected</li>
</ul>
<p>Writing the source and date for every row helps later when you clean the list, remove duplicates and decide what to refresh.</p>
<h2>Step 4: Find and enrich the email addresses</h2>
<p>Often you have a name and a company website but no email. There are three common ways to fill the gap:</p>
<ul>
<li>Look for the address on the website, such as contact or team pages.</li>
<li>Use the company's email pattern. Many companies use something like first name at the domain or first initial plus last name at the domain. Try the most likely patterns, but never guess blindly and send.</li>
<li>Use an enrichment tool or service that returns a verified email for a person at a company.</li>
</ul>
<p>Whatever method you use, treat the result as unconfirmed until it passes verification in the next step.</p>
<h2>Step 5: Clean and verify before you send</h2>
<p>This step protects your domains. Remove duplicates, blank rows and obviously broken addresses. Then run the list through a bulk verifier and split the results into valid, catch all, risky and invalid groups. Send only to valid addresses first, and keep catch all and risky ones in a separate file.</p>
<p>I explained this process in detail in my guide on <a href="https://tqnexus.hashnode.dev/how-to-verify-a-scraped-b2b-email-list-before-you-send-a-single-cold-email">verifying a scraped B2B email list</a>. Do not skip it, because a high bounce rate can damage your sender reputation for months.</p>
<h2>Step 6: Segment the list before you write</h2>
<p>Do not send one message to everyone. Split the list into smaller groups that share something real, such as the same industry, the same job title or the same problem. A short message written for one clear group almost always gets a better reply than a general message sent to a mixed list.</p>
<h2>Legal and ethical basics</h2>
<p>This is general information and not legal advice, so check the rules for your own market.</p>
<ul>
<li>Focus on business contact data tied to a work role, not private personal information.</li>
<li>Respect website terms and do not collect data behind logins or paywalls.</li>
<li>In the EU and UK, data protection rules apply to business contacts, and in Germany business email marketing generally needs consent, so a different approach is often needed.</li>
<li>Always include a simple way to opt out in your campaigns, and remove anyone who asks to stop.</li>
</ul>
<h2>Common mistakes to avoid</h2>
<ul>
<li>Buying a huge list with no information about where the data came from.</li>
<li>Collecting everything and defining your ideal customer later.</li>
<li>Sending without verifying the emails.</li>
<li>Using old data. B2B contacts change jobs often, so refresh older lists before use.</li>
<li>Mixing very different audiences in one campaign.</li>
</ul>
<h2>When to hand it off</h2>
<p>Building a good list takes time and tools, and doing it badly is expensive. If you would rather focus on your offer and your sales calls, I build lists for clients through my <a href="https://tqnexus.com/data-scraping-service.php">data scraping service</a>, with every address checked through my <a href="https://tqnexus.com/email-verification-service.php">email verification service</a>. If you want the full outbound system on top, including sending setup and reply handling, see my <a href="https://tqnexus.com/lead-generation-agency.php">lead generation agency</a> page.</p>
]]></content:encoded></item><item><title><![CDATA[How Many Domains and Mailboxes Do You Need for Cold Email?]]></title><description><![CDATA[A simple formula to size your cold email setup: how many sending domains and mailboxes you need, plus the DNS and warmup basics that avoid spam.]]></description><link>https://tqnexus.hashnode.dev/how-many-domains-and-mailboxes-do-you-need-for-cold-email</link><guid isPermaLink="true">https://tqnexus.hashnode.dev/how-many-domains-and-mailboxes-do-you-need-for-cold-email</guid><category><![CDATA[cold email]]></category><category><![CDATA[email deliverability]]></category><category><![CDATA[b2b]]></category><category><![CDATA[lead generation]]></category><dc:creator><![CDATA[TQ Nexus LLC]]></dc:creator><pubDate>Tue, 17 Nov 2026 07:52:55 GMT</pubDate><content:encoded><![CDATA[<p>If you plan to send cold email at any real volume, the first question is not what to write. It is how many sending domains and mailboxes you need. Get this wrong and you either burn your main domain in a few weeks or pay for far more infrastructure than you use.</p>
<p>This guide gives you a simple formula to size your setup, plus the domain, DNS and warmup basics that keep your emails out of spam.</p>
<h2>Why you should never cold email from your main domain</h2>
<p>Your main domain is your brand. It sends your invoices, proposals and replies to real customers. If cold email from that domain triggers spam complaints or high bounces, mailbox providers lower the reputation of the whole domain, and your normal emails suffer too.</p>
<p>The standard approach is to buy separate sending domains that look close to your brand, send cold email only from those, and keep your main domain clean. If one sending domain gets damaged, you replace it and nothing important is affected.</p>
<h2>The simple formula to size your setup</h2>
<p>Start with how many cold emails you want to send per day, then work backwards.</p>
<ol>
<li><strong>Pick a safe volume per mailbox.</strong> A common conservative guideline is 30 to 40 cold emails per day per mailbox once it is warmed up. Going higher is possible, but it raises risk quickly.</li>
<li><strong>Divide your daily target by that number.</strong> If you want to send 300 emails per day and each mailbox sends 35, you need about 9 mailboxes.</li>
<li><strong>Keep 2 to 3 mailboxes per domain.</strong> Too many mailboxes on one domain concentrates the risk. For 9 mailboxes, that means 3 sending domains with 3 mailboxes each.</li>
</ol>
<p>These are rules of thumb, not guarantees. Providers change their filters, so treat the numbers as a safe starting point and adjust from your own bounce and reply data.</p>
<h2>Quick sizing guide</h2>
<ul>
<li>Around 100 emails per day: 3 mailboxes on 1 or 2 domains</li>
<li>Around 300 emails per day: 9 mailboxes on 3 domains</li>
<li>Around 1,000 emails per day: 30 mailboxes on 10 domains</li>
</ul>
<p>More volume is not always better. A smaller, well targeted campaign on a clean list often brings more replies than a huge blast.</p>
<h2>How to choose sending domains</h2>
<ul>
<li>Use a name close to your brand, such as a "get" or "try" version of your company name, so the sender still looks trustworthy.</li>
<li>Stick to common endings like .com. Unusual endings can look suspicious to filters and to people.</li>
<li>Point each sending domain to your main website with a simple redirect, so anyone who checks it finds a real company.</li>
<li>Avoid names that look like they copy another company. Use your own brand.</li>
</ul>
<h2>The DNS setup every sending domain needs</h2>
<p>Before a single email goes out, each domain needs three records:</p>
<ul>
<li><strong>SPF</strong> tells receiving servers which servers may send mail for your domain.</li>
<li><strong>DKIM</strong> adds a signature so the message can be verified as unaltered.</li>
<li><strong>DMARC</strong> tells providers what to do if SPF or DKIM checks fail, and gives you reports.</li>
</ul>
<p>Missing or wrong records are one of the most common reasons cold emails land in spam. Test your records after setup, not after your first campaign.</p>
<h2>Warmup: do not skip it</h2>
<p>A brand new mailbox has no sending history, so jumping straight to 40 emails per day looks like spam behavior. Warm each mailbox slowly:</p>
<ul>
<li>Week 1: send a few emails per day, mostly warmup traffic</li>
<li>Weeks 2 to 3: raise the volume step by step</li>
<li>After 3 to 4 weeks: move to your target volume and keep warmup running in the background</li>
</ul>
<p>Watch the numbers each day. If bounces or spam placement get worse, slow down instead of pushing through.</p>
<h2>Mistakes that burn domains</h2>
<ul>
<li>Sending to an unverified list. Even a perfect setup fails if half the addresses bounce. I explained how to clean a list in my guide on <a href="https://tqnexus.hashnode.dev/how-to-verify-a-scraped-b2b-email-list-before-you-send-a-single-cold-email">verifying a scraped B2B email list</a>.</li>
<li>Putting too many mailboxes on one domain.</li>
<li>Ramping up volume too fast in the first month.</li>
<li>Sending the same copy to everyone. Personalized, relevant messages get better replies and fewer complaints.</li>
<li>Ignoring bounce and reply numbers after launch.</li>
</ul>
<h2>Final thoughts</h2>
<p>Good cold email infrastructure is boring on purpose: separate domains, correct DNS records, patient warmup and sensible daily limits. When these basics are right, your campaign results depend on your offer and your targeting instead of your deliverability.</p>
<p>If you would rather not build this yourself, I set it up for clients as part of my <a href="https://tqnexus.com/cold-email-infrastructure.php">cold email infrastructure service</a>, and I run campaigns on top of it through <a href="https://tqnexus.com/cold-outreach.php">cold email outreach management</a>. For the list side, see my <a href="https://tqnexus.com/email-verification-service.php">email verification service</a>.</p>
]]></content:encoded></item><item><title><![CDATA[How to Verify a Scraped B2B Email List Before You Send a Single Cold Email]]></title><description><![CDATA[How to clean and verify a scraped B2B email list so your cold email bounce rate stays low and your domains stay healthy.]]></description><link>https://tqnexus.hashnode.dev/how-to-verify-a-scraped-b2b-email-list-before-you-send-a-single-cold-email</link><guid isPermaLink="true">https://tqnexus.hashnode.dev/how-to-verify-a-scraped-b2b-email-list-before-you-send-a-single-cold-email</guid><category><![CDATA[cold email]]></category><category><![CDATA[email verification]]></category><category><![CDATA[B2B marketing]]></category><category><![CDATA[lead generation]]></category><category><![CDATA[cold email marketing]]></category><dc:creator><![CDATA[TQ Nexus LLC]]></dc:creator><pubDate>Mon, 16 Nov 2026 09:32:09 GMT</pubDate><content:encoded><![CDATA[<p>A scraped email list should never go straight into a cold email tool: verify it first, clean out the risky addresses, and send in small batches, so your bounce rate stays low and your domains stay healthy.</p>
<h2>Why verification comes first</h2>
<p>Most cold email problems start before the first email is written. When you scrape a B2B list from public sources, a share of the addresses will be outdated, mistyped, or guessed from a pattern. Send to them and the mail server answers with a bounce.</p>
<p>Mailbox providers watch your bounce rate. A high rate tells them you are sending to people you do not know, and your emails start landing in spam or get blocked. A common rule of thumb in cold email is to keep hard bounces under 2 percent. Verification is how you stay there.</p>
<p>I work with scraped and enriched data every week, and the pattern is always the same: the lists that get verified properly are the ones whose campaigns stay healthy for months.</p>
<h2>What the verification results mean</h2>
<p>Most verification tools sort every address into a few groups. Names differ slightly between tools, but the logic is the same.</p>
<ul>
<li><strong>Valid:</strong> The mailbox exists and accepts mail. Safe to send.</li>
<li><strong>Invalid:</strong> The mailbox does not exist or the domain is dead. Remove it.</li>
<li><strong>Catch all:</strong> The domain accepts mail for any address, so the tool cannot confirm the person. Send carefully, in a separate small batch.</li>
<li><strong>Risky or unknown:</strong> The server did not answer clearly, or the address is a role account like info@. Test in a small batch or remove.</li>
</ul>
<p>The catch all group is where most people get hurt. It can look like a large part of your list, but you cannot tell which addresses really exist. I keep these apart from the valid group and never mix them into the first send.</p>
<h2>My 5 step verification workflow</h2>
<ol>
<li><strong>Clean the raw file first.</strong> Remove duplicates, blank rows and obviously broken addresses (missing @, spaces, typos like .con). This saves verification credits.</li>
<li><strong>Run a first verification pass.</strong> Upload the list to a bulk verifier such as MillionVerifier or DeBounce. Download the result file with the status column.</li>
<li><strong>Split the list by result.</strong> Keep valid addresses in one file. Put catch all and risky addresses in a second file. Delete invalid ones.</li>
<li><strong>Remove role accounts and risky patterns.</strong> Addresses like info@, sales@ or admin@ rarely reach a decision maker and are more likely to complain. Remove them or keep them out of the first campaign.</li>
<li><strong>Re verify older data.</strong> If a list is more than a few weeks old, run it again before sending. B2B contacts change jobs and companies close, so a clean list goes stale quickly.</li>
</ol>
<p>When the list is clean, do not send everything at once. Start with a small batch, watch the bounce and reply numbers for a few days, then scale up. If the bounce rate climbs, pause and check the list before you send more.</p>
<h2>Common mistakes that burn domains</h2>
<ul>
<li><strong>Sending the same day you scrape.</strong> Data needs cleaning and verification first, always.</li>
<li><strong>Trusting one tool blindly.</strong> No verifier is perfect. For important lists, a second check on the valid group catches extra problems.</li>
<li><strong>Treating catch all as valid.</strong> It is a maybe, not a yes.</li>
<li><strong>Using your main company domain.</strong> Run cold email from separate sending domains, set up with SPF, DKIM and DMARC, so a problem never touches your main domain. I covered the setup in my guide to <a href="https://tqnexus.com/cold-email-infrastructure.php">cold email infrastructure</a>.</li>
<li><strong>Ignoring bounces after the send.</strong> Remove bounced addresses from the list right away and check the numbers every day in the first week.</li>
</ul>
<h2>Quick checklist before you hit send</h2>
<ul>
<li>Duplicates and broken rows removed</li>
<li>List verified within the last few weeks</li>
<li>Invalid addresses deleted</li>
<li>Catch all and risky addresses kept in a separate file</li>
<li>Role accounts removed or held back</li>
<li>Sending from separate domains with SPF, DKIM and DMARC in place</li>
<li>First send is a small batch, with bounce and reply rates checked daily</li>
</ul>
<p>Getting this routine right costs a little time up front and saves you from burned domains later. If you would rather hand it off, I run this process for clients as an <a href="https://tqnexus.com/email-verification-service.php">email verification service</a>, and I also build lists from scratch through <a href="https://tqnexus.com/data-scraping-service.php">data scraping and enrichment</a>.</p>
]]></content:encoded></item></channel></rss>