3 Commits

Author SHA1 Message Date
1e7907d8fa Add Insights article: HOA Financial Fraud Prevention: The Internal Controls Every Board Needs (2026-09-15)
- New article: articles/hoa-fraud-prevention-internal-controls.html
- Updated articles/index.html with new card (newest first)
- Updated sitemap.xml with new URL entry

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-15 09:05:16 -04:00
614a0edfa1 Merge pull request 'Block example.com emails and homesites under 10' (#26) from feature/block-example-domain-and-min-homesites into main
All checks were successful
Deploy to Production / deploy (push) Successful in 3s
2026-07-24 09:30:44 -04:00
1219117adf Block example.com emails and homesites under 10
Spam submissions were still getting through with placeholder data. Two
more content filters on the public form endpoints:

- Reject emails from reserved documentation domains (example.com/.org/
  /.net/.edu and subdomains) and reserved TLDs (.test/.example/.invalid/
  localhost). testing@example.com and friends are never real leads.
- Reject a homesites count below 10. Real associations are larger; the
  junk uses 0/1/2.

Both are validated server-side in security.js (validateEmail gains a
domain blocklist, new validateHomesites) and mirrored client-side in
app.js for immediate feedback. The homesites input min attribute goes
from 1 to 10. Blocked submissions return 400 with a `field` hint and
store nothing.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-24 09:30:15 -04:00
7 changed files with 374 additions and 6 deletions

25
app.js
View File

@@ -125,12 +125,24 @@
// gives immediate feedback instead of a round-trip. // gives immediate feedback instead of a round-trip.
const EMAIL_RX = /^[A-Za-z0-9](?:[A-Za-z0-9._%+-]{0,62}[A-Za-z0-9])?@[A-Za-z0-9](?:[A-Za-z0-9-]{0,61}[A-Za-z0-9])?(?:\.[A-Za-z0-9](?:[A-Za-z0-9-]{0,61}[A-Za-z0-9])?)*\.[A-Za-z]{2,24}$/; const EMAIL_RX = /^[A-Za-z0-9](?:[A-Za-z0-9._%+-]{0,62}[A-Za-z0-9])?@[A-Za-z0-9](?:[A-Za-z0-9-]{0,61}[A-Za-z0-9])?(?:\.[A-Za-z0-9](?:[A-Za-z0-9-]{0,61}[A-Za-z0-9])?)*\.[A-Za-z]{2,24}$/;
// Reserved documentation domains / TLDs — mirrors security.js. Real leads
// never come from these; spam bots use them.
const BLOCKED_EMAIL_DOMAINS = ['example.com', 'example.org', 'example.net', 'example.edu'];
const BLOCKED_EMAIL_TLDS = ['test', 'example', 'invalid', 'localhost'];
function isValidEmail(v) { function isValidEmail(v) {
if (v.length > 254 || v.indexOf('@') > 64) return false; if (v.length > 254 || v.indexOf('@') > 64) return false;
if (v.includes('..')) return false; if (v.includes('..')) return false;
return EMAIL_RX.test(v); if (!EMAIL_RX.test(v)) return false;
const domain = v.slice(v.indexOf('@') + 1).toLowerCase();
const tld = domain.slice(domain.lastIndexOf('.') + 1);
if (BLOCKED_EMAIL_TLDS.includes(tld)) return false;
if (BLOCKED_EMAIL_DOMAINS.some(d => domain === d || domain.endsWith('.' + d))) return false;
return true;
} }
const MIN_HOMESITES = 10;
function showCalcError(msg) { function showCalcError(msg) {
if (!calcErr) return; if (!calcErr) return;
calcErr.textContent = msg; calcErr.textContent = msg;
@@ -159,6 +171,12 @@
return; return;
} }
if (homesites < MIN_HOMESITES) {
showCalcError(`Please enter the number of homesites in your community (minimum ${MIN_HOMESITES}).`);
document.getElementById('calcHomesites')?.focus();
return;
}
// Email is optional, but anything entered must be a real address. // Email is optional, but anything entered must be a real address.
if (calcEmail && !isValidEmail(calcEmail)) { if (calcEmail && !isValidEmail(calcEmail)) {
showCalcError('Please enter a valid email address.'); showCalcError('Please enter a valid email address.');
@@ -243,10 +261,11 @@
// is stored. AI/service errors (502/503) fall through to the local result. // is stored. AI/service errors (502/503) fall through to the local result.
if (!res.ok) { if (!res.ok) {
const data = await res.json().catch(() => ({})); const data = await res.json().catch(() => ({}));
if (data.blocked || data.field === 'email') { if (data.blocked || data.field) {
setCalcLoading(false); setCalcLoading(false);
showCalcError(data.error || 'We could not verify this submission. Please try again.'); showCalcError(data.error || 'We could not verify this submission. Please try again.');
if (data.field === 'email') document.getElementById('calcEmail')?.focus(); if (data.field === 'email') document.getElementById('calcEmail')?.focus();
if (data.field === 'homesites') document.getElementById('calcHomesites')?.focus();
resetCaptcha(); resetCaptcha();
await fetchFormToken(); // tokens are single-use; issue a fresh one await fetchFormToken(); // tokens are single-use; issue a fresh one
return; return;

View File

@@ -0,0 +1,278 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>HOA Financial Fraud Prevention: Internal Controls Every Board Needs | HOA LedgerIQ Insights</title>
<meta name="description" content="Embezzlement rarely starts with a criminal mastermind — it starts with one signature and nobody double-checking. Here's how HOA boards build real internal controls." />
<meta name="keywords" content="HOA fraud prevention, HOA embezzlement, HOA internal controls, HOA financial oversight, segregation of duties HOA, HOA audit trail, community association fraud" />
<link rel="canonical" href="https://www.hoaledgeriq.com/articles/hoa-fraud-prevention-internal-controls" />
<link rel="preconnect" href="https://fonts.googleapis.com" />
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700;800;900&display=swap" rel="stylesheet" />
<link rel="stylesheet" href="../styles.css" />
<!-- Open Graph -->
<meta property="og:title" content="HOA Financial Fraud Prevention: The Internal Controls Every Board Needs" />
<meta property="og:description" content="Embezzlement rarely starts with a criminal mastermind — it starts with one signature and nobody double-checking. Here's how to close that gap." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://www.hoaledgeriq.com/articles/hoa-fraud-prevention-internal-controls" />
<meta property="article:published_time" content="2026-09-15" />
<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-RTWNVXPMRF"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-RTWNVXPMRF');
</script>
</head>
<body>
<!-- NAV -->
<nav class="nav">
<div class="nav-inner">
<a href="../index.html" class="nav-logo">
<img src="../logo_house_transparent.svg" alt="HOA LedgerIQ" class="logo-img" />
</a>
<ul class="nav-links">
<li><a href="../index.html">Home</a></li>
<li><a href="../index.html#features">Features</a></li>
<li><a href="../index.html#pricing">Pricing</a></li>
<li><a href="index.html" class="nav-active">Insights</a></li>
</ul>
<a href="https://app.hoaledgeriq.com/pricing" class="btn btn-primary nav-btn" target="_blank" rel="noopener">Start Free Trial</a>
<a href="https://app.hoaledgeriq.com" class="btn btn-outline nav-btn nav-login" target="_blank" rel="noopener">Login</a>
</div>
</nav>
<!-- ARTICLE HEADER -->
<header class="article-header">
<div class="container">
<div class="article-breadcrumb">
<a href="index.html">← Back to Insights</a>
</div>
<div class="article-tag">Board Management</div>
<h1 class="article-title">HOA Financial Fraud Prevention<br /><span class="gradient-text">The Internal Controls Every Board Needs</span></h1>
<p class="article-subtitle">Embezzlement rarely starts with a criminal mastermind. It starts with one signature, one account, and nobody else looking. Here's how to close that gap.</p>
<div class="article-meta">
<span class="article-meta-author">HOA LedgerIQ Team</span>
<span class="article-meta-separator"></span>
<span>September 15, 2026</span>
<span class="article-meta-separator"></span>
<span>9 min read</span>
</div>
</div>
</header>
<!-- ARTICLE BODY: INTRO + SECTIONS 1-2 -->
<section class="article-body-section">
<div class="container">
<div class="article-prose">
<p>Every HOA board eventually has this conversation, usually in a hushed tone after a meeting has officially ended: "Have you ever actually looked at the bank statements, or do we just trust that the numbers in the report match?" More often than anyone would like to admit, the honest answer is that nobody has checked. The treasurer says the numbers are right, the board believes the treasurer, and the assumption gets passed down year after year, board term after board term, until it simply becomes how things are done.</p>
<p>That assumption is exactly the gap that HOA fraud slips through. It's a pattern that shows up in local news stories with depressing regularity: a well-liked, long-serving treasurer, trusted implicitly by neighbors who considered them a friend, quietly moves association funds into a personal account over months or years. Nobody suspected anything because nobody was structurally required to look. The fraud isn't usually discovered by an alert board member catching a discrepancy — it's discovered when that treasurer finally steps down and someone new opens the books for the first time.</p>
<p>This isn't a story about bad people. Most HOA treasurers are honest, and the overwhelming majority of community associations never experience fraud. But HOAs share a structural vulnerability that makes them unusually easy targets when something does go wrong: a single volunteer, often unpaid and rarely trained in accounting, frequently holds sole control over both the checkbook and the books that describe what the checkbook did. There's no separate finance department. No compliance officer. No second set of eyes required by policy. Trust becomes the entire control system — and trust, on its own, isn't a control at all.</p>
<p>The good news is that the fix isn't complicated, expensive, or a reflection on anyone's integrity. It's a small number of structural habits that, once in place, make fraud dramatically harder to commit and dramatically easier to catch early if it happens anyway. Here's what those habits look like.</p>
<h2>Why HOAs Are an Easy Target</h2>
<p>Picture the typical financial workflow in a self-managed HOA. The treasurer receives assessment payments, deposits them, pays the vendors, reconciles the bank account, and prepares the report the board sees at the meeting. One person touches every step. There is no moment in that chain where a second, independent set of eyes is structurally required to see what happened before the money has already moved.</p>
<p>Compare that to how a business — even a small one — typically handles money. The person who approves an expense usually isn't the same person who cuts the check, and neither of them is usually the person who reconciles the bank statement at month's end. That separation exists specifically because it makes fraud require collusion between multiple people rather than the judgment lapse of one. HOAs, run by volunteers with limited time and no formal training, tend to collapse all of those roles into whoever raised their hand to be treasurer.</p>
<p>Add to that the informality of most treasurer handoffs. When a volunteer treasurer's term ends, the transition is often a folder of documents and a login password, not a reconciled audit trail reviewed by an outgoing and incoming officer together. Years of financial history can pass from person to person without anyone outside that role ever independently verifying that the numbers on the report matched the numbers in the bank.</p>
<div class="highlight-box">
<p><strong>The uncomfortable truth:</strong> in most HOA fraud cases that eventually make the news, the controls that would have caught it early weren't complicated. They just didn't exist. A single reconciliation review by someone other than the treasurer would very likely have surfaced the problem within months instead of years.</p>
</div>
<h2>Segregation of Duties: The One Control That Matters Most</h2>
<p>If a board can only adopt one control this year, this is the one. Segregation of duties means no single person handles a financial transaction from start to finish without at least one other set of eyes involved somewhere in the process. It doesn't require hiring anyone or spending money — it requires distributing existing responsibilities across more than one board member.</p>
<p>In practice, this looks like: the treasurer prepares payments, but a second board member (often the president or vice president) reviews and co-signs checks or approves electronic payments above a set threshold. The person who deposits incoming assessment payments isn't the only person who ever sees the bank statement — someone else on the board reviews it independently each month, not just the treasurer's summary of it. Vendor additions and changes to banking information require sign-off from more than one person, since redirecting a legitimate vendor payment to a fraudulent account is one of the more common fraud patterns in any small organization.</p>
<p>None of this implies distrust of the treasurer. It's the same logic behind why pilots use pre-flight checklists even after thousands of hours of experience, and why publicly traded companies require independent auditors even when their own accounting staff is excellent. Good controls protect honest people as much as they deter dishonest ones — an honest treasurer who is the sole financial gatekeeper is also the person who gets unfairly blamed for any discrepancy nobody else was positioned to catch earlier.</p>
<div class="highlight-box">
<p><strong>A simple starting rule:</strong> no payment above a set dollar threshold — many communities use $500 to $1,000 — should go out without a second board member's review and approval, and no one person should be able to both initiate a payment and reconcile the account it came from.</p>
</div>
</div>
</div>
</section>
<!-- SECTIONS 3-5 -->
<section class="article-body-section" style="padding-top: 0;">
<div class="container">
<div class="article-prose">
<h2>The Documentation Habit Most Boards Skip</h2>
<p>Segregation of duties prevents fraud. Documentation catches it early if prevention fails. Most HOAs already generate more useful documentation than they realize — the problem is that nobody is required to actually look at it on a regular schedule.</p>
<p>A monthly bank reconciliation, reviewed by someone other than the person who prepared it, is the single most powerful early-detection tool available to a volunteer board. This doesn't need to be a forensic audit. It's a straightforward comparison: does the ending balance on the bank statement match the ending balance in the association's books? Do all the transactions in one appear in the other? Is anything unfamiliar — a vendor nobody recognizes, a check number out of sequence, a transfer nobody remembers approving? This kind of review takes a board member 20 to 30 minutes a month and is the reason most fraud, when it does occur, gets caught within a matter of months rather than years in communities that actually do it.</p>
<p>Beyond monthly reconciliation, a complete audit trail matters more than most boards appreciate until they need one. Every transaction should have a timestamp, a record of who initiated it, and — for payments — a record of who approved it. This isn't about creating paperwork for its own sake. It's about making sure that if a question ever comes up, whether from a suspicious homeowner, an incoming board, or an actual investigation, the answer already exists in a form nobody has to reconstruct from memory.</p>
<blockquote>"We didn't think we needed an audit trail because we trusted our treasurer completely. We were right to trust her — but when a homeowner asked a pointed question at an annual meeting, having the timestamped record meant we could answer in the room instead of promising to 'look into it' and hoping the question didn't come up again."</blockquote>
<div class="highlight-box">
<p><strong>What good documentation buys a board:</strong> not just fraud detection, but the ability to answer any homeowner's question about where the money went — instantly, with a record, rather than a reassurance that requires trust nobody outside the treasurer's role can independently verify.</p>
</div>
<h2>What Oversight Actually Looks Like at the Board Table</h2>
<p>Controls only work if someone is actually exercising them, which means the board as a whole — not just the treasurer — has to build financial oversight into its regular rhythm. This doesn't require every board member to become an accountant. It requires a handful of habits that turn oversight from an abstract responsibility into something that actually happens every month.</p>
<p>Every board meeting should include a genuine review of the financials, not a rubber-stamp acceptance of a report nobody reads closely. At least one board member other than the treasurer should be reviewing the bank statement independently each month, as described above. Many well-run associations also bring in an independent CPA to perform a review or compilation annually — not a full audit, which can be costly for smaller communities, but a level of outside scrutiny appropriate to the association's size. And treasurer transitions should include a formal handoff meeting where outgoing and incoming officers, ideally alongside a third board member, walk through the current reconciliation together before anyone signs off that everything is in order.</p>
<p>It's also worth having an honest conversation, once a year, about what would happen if something did go wrong. Does the association carry fidelity bond or crime insurance covering employee or volunteer theft? Many HOA insurance policies include this coverage by default, but plenty of boards have never confirmed it, and some governing documents or state statutes actually require a minimum coverage amount that nobody has checked in years.</p>
<div class="highlight-box">
<p><strong>What technology changes:</strong> a platform that logs every transaction automatically, flags unusual activity, and gives every board member — not just the treasurer — real-time visibility into the books removes the dependency on any one person's memory or goodwill. HOA LedgerIQ's audit trail keeps a timestamped record of every entry and every approval, so oversight doesn't depend on someone remembering to ask the right question.</p>
</div>
</div>
</div>
</section>
<!-- SCREENSHOT CAROUSEL -->
<section class="article-showcase">
<div class="container">
<div class="article-showcase-header">
<div class="section-label">See It in Action</div>
<h2>Financial Oversight That Doesn't Depend on Memory</h2>
<p>A complete, timestamped audit trail and real-time dashboards give every board member visibility — not just the person holding the checkbook.</p>
</div>
<div class="screenshot-carousel" id="screenshotCarousel">
<div class="carousel-frame">
<div class="carousel-slides">
<div class="carousel-slide active">
<img src="../img/screenshot-dashboard.png" alt="HOA LedgerIQ Dashboard — Fund health scores, operating and reserve balances" />
<div class="slide-caption">Dashboard — Real-Time Visibility for Every Board Member</div>
</div>
<div class="carousel-slide">
<img src="../img/screenshot-cashflow.png" alt="HOA LedgerIQ Cash Flow — Actuals and forward projections" />
<div class="slide-caption">Cash Flow — Actuals &amp; Forward Projections</div>
</div>
<div class="carousel-slide">
<img src="../img/screenshot-capital.png" alt="HOA LedgerIQ Capital Planning — Multi-year project timeline and budget view" />
<div class="slide-caption">Capital Planning — Multi-Year Project Timeline &amp; Budget</div>
</div>
</div>
</div>
<div class="carousel-controls">
<button class="carousel-btn carousel-prev" aria-label="Previous screenshot">&#8592;</button>
<div class="carousel-dots">
<span class="carousel-dot active" data-index="0"></span>
<span class="carousel-dot" data-index="1"></span>
<span class="carousel-dot" data-index="2"></span>
</div>
<button class="carousel-btn carousel-next" aria-label="Next screenshot">&#8594;</button>
</div>
</div>
</div>
</section>
<!-- ARTICLE BODY: PRACTICE + CONCLUSION -->
<section class="article-body-section">
<div class="container">
<div class="article-prose">
<h2>What This Looks Like in Practice</h2>
<p>Consider a 90-unit community that decides, after a scare at a neighboring HOA made the local news, to formalize its financial controls. The board doesn't hire anyone new or spend a dollar on the change. It simply agrees on a handful of new habits.</p>
<p>The treasurer still handles the day-to-day bookkeeping and initiates payments, but the vice president now reviews and co-approves anything over $750 before it goes out, and reviews the bank statement independently each month rather than only reading the treasurer's summary at the meeting. Vendor banking changes now require a two-person sign-off after the board realizes, during the conversation, that they'd never actually verified how a wire redirect request would be caught if one ever came in by email — a scam that has hit other HOAs and small nonprofits with alarming frequency.</p>
<p>Six months in, the independent bank review catches a bookkeeping error — not fraud, just a misapplied vendor payment — within three weeks of it happening, instead of at year-end reconciliation the way it would have gone unnoticed before. The board fixes it in an afternoon. At the annual meeting, when a homeowner asks pointedly where a specific special assessment payment went, the treasurer pulls up the timestamped record in seconds instead of promising to follow up later. Nobody at that meeting realizes how much smoother that exchange was than it would have been a year earlier — which is exactly the point. Good controls are supposed to be invisible when nothing has gone wrong, and instantly available the moment something needs to be checked.</p>
<h2>Trust, But Build the System Anyway</h2>
<p>No board wants to treat its treasurer like a suspect, and building internal controls doesn't require that mindset. The entire point of segregation of duties, monthly reconciliation review, and a real audit trail is that they protect everyone involved — the community's money, certainly, but also the volunteer who would otherwise carry the full, unverifiable weight of "just trust me" for as long as they hold the role.</p>
<p>The communities that get burned by HOA fraud are rarely the ones with suspicious treasurers. They're the ones that never got around to building a system that didn't depend entirely on trust in the first place. That's a fixable gap, and closing it costs a board nothing but the discipline to make oversight a habit rather than an assumption.</p>
</div>
</div>
</section>
<!-- ARTICLE CTA -->
<section class="article-cta">
<div class="container">
<h2>Give Every Board Member Real Visibility.</h2>
<p>HOA LedgerIQ's automatic audit trail and real-time dashboards mean financial oversight never has to rely on one person's memory.</p>
<a href="https://app.hoaledgeriq.com/pricing" class="btn btn-primary btn-lg" target="_blank" rel="noopener">Start Your Free 14-Day Trial</a>
<p class="article-cta-note">No credit card required &nbsp;·&nbsp; 14-day free trial &nbsp;·&nbsp; No contracts</p>
</div>
</section>
<!-- ARTICLE BOTTOM NAV -->
<div class="insights-grid-section" style="padding: 2.5rem 0 3rem;">
<div class="container">
<div style="border-top: 1px solid rgba(255,255,255,0.07); padding-top: 2rem; display: flex; justify-content: space-between; align-items: center; flex-wrap: wrap; gap: 1rem;">
<a href="hoa-reserve-fund-health-score.html" style="color: var(--blue); font-size: 0.875rem; font-weight: 600; text-decoration: none; display: inline-flex; align-items: center; gap: 0.4rem; transition: opacity 0.2s;">← Previous: How to Read Your HOA's Reserve Fund Health Score</a>
<a href="index.html" style="color: var(--gray-400); font-size: 0.875rem; text-decoration: none; display: inline-flex; align-items: center; gap: 0.4rem; transition: color 0.2s;">All Insights →</a>
</div>
</div>
</div>
<!-- FOOTER -->
<footer class="footer">
<div class="container footer-inner">
<div class="footer-logo">
<img src="../logo_house.svg" alt="HOA LedgerIQ" class="logo-img logo-img--footer" />
<p>AI-powered HOA finance management.</p>
</div>
<div class="footer-links">
<div class="footer-col">
<div class="footer-col-title">Product</div>
<a href="../index.html#features">Features</a>
<a href="../index.html#pricing">Pricing</a>
<a href="https://app.hoaledgeriq.com/pricing" target="_blank" rel="noopener">Start Free Trial</a>
</div>
<div class="footer-col">
<div class="footer-col-title">Pages</div>
<a href="../investment-management.html">Investment Management</a>
<a href="../reserve-study-software.html">Reserve Studies</a>
<a href="index.html">Insights</a>
</div>
<div class="footer-col">
<div class="footer-col-title">Legal</div>
<a href="../privacy.html">Privacy Policy</a>
<a href="../terms.html">Terms of Service</a>
</div>
</div>
</div>
<div class="footer-bottom">
<div class="container">
<span>&copy; 2026 HOA LedgerIQ. All rights reserved.</span>
</div>
</div>
</footer>
<script src="../app.js"></script>
<!-- Support Chat Widget -->
<script>
(function(d,t) {
var BASE_URL="https://chat.hoaledgeriq.com";
var g=d.createElement(t),s=d.getElementsByTagName(t)[0];
g.src=BASE_URL+"/packs/js/sdk.js";
g.async = true;
s.parentNode.insertBefore(g,s);
g.onload=function(){
window.chatwootSDK.run({
websiteToken: '1QMW1fycL5xHvd6XMfg4Dbb4',
baseUrl: BASE_URL
})
}
})(document,"script");
</script>
</body>
</html>

View File

@@ -54,6 +54,21 @@
<div class="article-grid"> <div class="article-grid">
<!-- Article 11 — Newest first -->
<a href="hoa-fraud-prevention-internal-controls.html" class="article-card" style="text-decoration:none;">
<span class="article-card-tag">Board Management</span>
<h2 class="article-card-title">HOA Financial Fraud Prevention: The Internal Controls Every Board Needs</h2>
<p class="article-card-excerpt">Embezzlement rarely starts with a criminal mastermind — it starts with one signature, one account, and nobody else looking. Here's how boards build the segregation of duties and audit trail that close the gap.</p>
<div class="article-card-meta">
<span>HOA LedgerIQ Team</span>
<span class="article-card-meta-dot"></span>
<span>September 15, 2026</span>
<span class="article-card-meta-dot"></span>
<span>9 min read</span>
</div>
<span class="article-card-read-more">Read article →</span>
</a>
<!-- Article 10 — Newest first --> <!-- Article 10 — Newest first -->
<a href="hoa-reserve-fund-health-score.html" class="article-card" style="text-decoration:none;"> <a href="hoa-reserve-fund-health-score.html" class="article-card" style="text-decoration:none;">
<span class="article-card-tag">Reserve Funds</span> <span class="article-card-tag">Reserve Funds</span>

View File

@@ -469,7 +469,7 @@
<div class="calc-grid"> <div class="calc-grid">
<div class="calc-field"> <div class="calc-field">
<label for="calcHomesites">Number of homesites</label> <label for="calcHomesites">Number of homesites</label>
<input type="number" id="calcHomesites" placeholder="e.g. 150" min="1" /> <input type="number" id="calcHomesites" placeholder="e.g. 150" min="10" />
</div> </div>
<div class="calc-field"> <div class="calc-field">
<label for="calcPropertyType">Property type</label> <label for="calcPropertyType">Property type</label>

View File

@@ -147,6 +147,8 @@ const MESSAGES = {
email_required: 'Please enter your email address.', email_required: 'Please enter your email address.',
email_invalid: 'Please enter a valid email address.', email_invalid: 'Please enter a valid email address.',
email_too_long: 'That email address is too long.', email_too_long: 'That email address is too long.',
email_blocked: 'Please use a valid work or personal email address.',
homesites_too_low: 'Please enter the number of homesites in your community (minimum 10).',
}; };
const STATUS = { rate_limited: 429, honeypot: 400 }; const STATUS = { rate_limited: 429, honeypot: 400 };
@@ -167,6 +169,26 @@ const EMAIL_RX = /^[A-Za-z0-9](?:[A-Za-z0-9._%+-]{0,62}[A-Za-z0-9])?@[A-Za-z0-9]
// C0/C1 control characters and DEL — includes the CR/LF used for header injection. // C0/C1 control characters and DEL — includes the CR/LF used for header injection.
const CONTROL_CHARS_RX = /[\x00-\x1F\x7F-\x9F]/; const CONTROL_CHARS_RX = /[\x00-\x1F\x7F-\x9F]/;
// Domains that are never a real lead. These are the IANA reserved documentation
// domains (RFC 2606) plus reserved TLDs, which is what spam bots reach for.
// A submitted domain is blocked when it equals one of these or is a subdomain
// of one (e.g. `mail.example.com`).
const BLOCKED_EMAIL_DOMAINS = new Set([
'example.com', 'example.org', 'example.net', 'example.edu',
]);
const BLOCKED_EMAIL_TLDS = new Set(['test', 'example', 'invalid', 'localhost']);
function isBlockedDomain(domain) {
const d = domain.toLowerCase();
const tld = d.slice(d.lastIndexOf('.') + 1);
if (BLOCKED_EMAIL_TLDS.has(tld)) return true;
for (const blocked of BLOCKED_EMAIL_DOMAINS) {
if (d === blocked || d.endsWith('.' + blocked)) return true;
}
return false;
}
/** /**
* Validate an email address. * Validate an email address.
* Returns { ok: true, email } with the normalised (trimmed, lower-cased) value, * Returns { ok: true, email } with the normalised (trimmed, lower-cased) value,
@@ -204,10 +226,28 @@ function validateEmail(raw, { required = true } = {}) {
if (local.length > 64 || domain.length > 253) return { ok: false, reason: 'email_too_long' }; if (local.length > 64 || domain.length > 253) return { ok: false, reason: 'email_too_long' };
if (email.includes('..')) return { ok: false, reason: 'email_invalid' }; if (email.includes('..')) return { ok: false, reason: 'email_invalid' };
if (!EMAIL_RX.test(email)) return { ok: false, reason: 'email_invalid' }; if (!EMAIL_RX.test(email)) return { ok: false, reason: 'email_invalid' };
if (isBlockedDomain(domain)) return { ok: false, reason: 'email_blocked' };
return { ok: true, email: email.toLowerCase() }; return { ok: true, email: email.toLowerCase() };
} }
// ── Homesites validation ─────────────────────────────────
// Real associations have at least this many units; smaller values are the
// placeholder junk (0, 1, 2…) the spam submissions use.
const MIN_HOMESITES = 10;
/**
* Validate a homesites count.
* Returns { ok: true, homesites } (a finite number) or { ok: false, reason }.
*/
function validateHomesites(raw) {
const n = typeof raw === 'number' ? raw : parseFloat(raw);
if (!Number.isFinite(n) || n < MIN_HOMESITES) {
return { ok: false, reason: 'homesites_too_low' };
}
return { ok: true, homesites: n };
}
/** /**
* Run every protection layer for a public form POST. * Run every protection layer for a public form POST.
* Returns { ok: true, ip } or { ok: false, status, error, reason }. * Returns { ok: true, ip } or { ok: false, status, error, reason }.
@@ -276,6 +316,8 @@ module.exports = {
issueFormToken, issueFormToken,
guardSubmission, guardSubmission,
validateEmail, validateEmail,
validateHomesites,
MIN_HOMESITES,
messageFor, messageFor,
publicConfig, publicConfig,
clientIp, clientIp,

View File

@@ -234,10 +234,17 @@ app.post('/api/calculate', async (req, res) => {
} }
const cleanEmail = emailCheck.email; const cleanEmail = emailCheck.email;
if (!homesites || !annualIncome) { if (!annualIncome) {
return res.status(400).json({ error: 'homesites and annualIncome are required.' }); return res.status(400).json({ error: 'homesites and annualIncome are required.' });
} }
// Homesites must be a real community size; tiny/placeholder values are spam.
const homesitesCheck = security.validateHomesites(homesites);
if (!homesitesCheck.ok) {
console.warn(`[abuse] rejected homesites from ${guard.ip}: ${JSON.stringify(homesites)}`);
return res.status(400).json({ error: security.messageFor(homesitesCheck.reason), field: 'homesites' });
}
if (!aiClient) { if (!aiClient) {
saveCalcSubmission(null); saveCalcSubmission(null);
return res.status(503).json({ error: 'AI service not configured.' }); return res.status(503).json({ error: 'AI service not configured.' });

View File

@@ -37,11 +37,18 @@
<!-- Insights / Blog --> <!-- Insights / Blog -->
<url> <url>
<loc>https://www.hoaledgeriq.com/articles/</loc> <loc>https://www.hoaledgeriq.com/articles/</loc>
<lastmod>2026-07-15</lastmod> <lastmod>2026-09-15</lastmod>
<changefreq>weekly</changefreq> <changefreq>weekly</changefreq>
<priority>0.85</priority> <priority>0.85</priority>
</url> </url>
<url>
<loc>https://www.hoaledgeriq.com/articles/hoa-fraud-prevention-internal-controls</loc>
<lastmod>2026-09-15</lastmod>
<changefreq>monthly</changefreq>
<priority>0.80</priority>
</url>
<url> <url>
<loc>https://www.hoaledgeriq.com/articles/hoa-reserve-fund-health-score</loc> <loc>https://www.hoaledgeriq.com/articles/hoa-reserve-fund-health-score</loc>
<lastmod>2026-07-15</lastmod> <lastmod>2026-07-15</lastmod>