Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN (document or assets)FIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/1 IPs match cert SANREVIEW
BMulti-Resolver DNS SpeedMean 196ms across 3 resolvers (spread 170ms)REVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<!doctype html>
<html lang="en">
<head>
<script>
window.addEventListener('error', function(event) {
const errorDiv = document.createElement('div');
errorDiv.style.position = 'fixed';
errorDiv.style.top = '0';
errorDiv.style.left = '0';
errorDiv.style.zIndex = '999999';
errorDiv.style.background = 'red';
errorDiv.style.color = 'white';
errorDiv.style.padding = '20px';
errorDiv.style.width = '100%';
errorDiv.style.whiteSpace = 'pre-wrap';
errorDiv.innerText = "GLOBAL ERROR: " + event.error?.stack;
document.body.appendChild(errorDiv);
});
</script>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, viewport-fit=cover" />
<title>វត្តស្នាយដួច</title>
<meta name="theme-color" content="#028090" />
<link rel="icon" type="image/x-icon" href="./favicon.ico" />
<link rel="icon" type="image/png" sizes="32x32" href="./favicon-32x32.png" />
<link rel="icon" type="image/png" sizes="16x16" href="./favicon-16x16.png" />
<link rel="icon" type="image/svg+xml" href="./icon.svg" />
<link rel="shortcut icon" href="./favicon.ico" />
<link rel="apple-touch-icon" href="./icon.png" />
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="default" />
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link rel="preload" href="./fonts/KhmerOS_muollight.ttf" as="font" type="font/ttf" crossorigin="anonymous">
<link href="https://fonts.googleapis.com/css2?family=Battambang:wght@400;700&family=Koulen&family=Moul&family=Rajdhani:wght@300;400;500;600;700&display=swap" rel="stylesheet" crossorigin="anonymous">
<meta name="description" content="Temple donation records, expenses, and activities management." />
<meta property="og:title" content="វត្តស្នាយដួច" />
<meta property="og:description" content="Temple donation records, expenses, and activities management." />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary_large_image" />
<style>
body {
margin: 0;
padding: 0;
background-color: #FAFAFA;
}
#initial-loader {
display: flex;
flex-direction: column;
align-items: center;
justify-content: center;
height: 100vh;
width: 100vw;
font-family: system-ui, -apple-system, sans-serif;
background-color: #FAFAFA;
}
@media (prefers-color-scheme: dark) {
body { background-color: #0F172A; }
#initial-loader { background-color: #0F172A; }
.spinner {
border: 3px solid rgba(45, 212, 191, 0.2) !important;
border-top-color: #2DD4BF !important;
}
}
.spinner {
width: 40px;
height: 40px;
border: 3px solid rgba(2, 128, 144, 0.2);
border-top-color: #028090;
border-radius: 50%;
animation: spin 1s linear infinite;
margin-bottom: 16px;
}
@keyframes spin {
to { transform: rotate(360deg); }
}
.loading-text {
font-size: 14px;
font-weight: 600;
color: #A1A1AA;
animation: pulse 2s cubic-bezier(0.4, 0, 0.6, 1) infinite;
}
@keyframes pulse {
0%, 100% { opacity: 1; }
50% { opacity: .5; }
}
</style>
<script type="module" crossorigin src="./assets/index-Cd66_aKO.js"></script>
<link rel="modulepreload" crossorigin href="./assets/vendor-lucide-PAwUdqkq.js">
<link rel="modulepreload" crossorigin href="./assets/vendor-motion-DTuj7iN0.js">
<link rel="modulepreload" crossorigin href="./assets/vendor-export-BNqNNMe5.js">
<link rel="stylesheet" crossorigin href="./assets/index-V5FkCLfn.css">
<link rel="manifest" href="./manifest.webmanifest"><script id="vite-plugin-pwa:register-sw" src="./registerSW.js"></script></head>
<body>
<div id="root">
<div id="initial-loader">
<div class="spinner"></div>
<div class="loading-text">កំពុងដំណើរការ...</div>
</div>
</div>
</body>
</html>
BTLS Certificate Expiry & Recommendations81 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
ADNS Records1 A records, 191 ms lookupPASS
| A | 69.46.46.40 |
| AAAA | — |
| CNAME | — |
| NS | launch1.spaceship.net, launch2.spaceship.net |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+DNSSECSigned and validatingPASS
A+Redirect ChainNo redirects — direct accessPASS
https://watsnaydouch.site
247 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://watsnaydouch.site | 200 | 247 ms | HTTP/1.1 | railway-hikari |
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencewatsnaydouch.site — via Spaceship, Inc., 11 days old, hosted on RAILWAY - Railway, USPASS
346 days
September 2, 2027
81 days
Issued by Let's Encrypt
11 days
Registered September 2, 2026
Enabled
Protects against DNS spoofing
RAILWAY - Railway, US
ASN AS400940
69.46.46.40
Spaceship, Inc.
Expiry timeline
Recommended actions
- Newly registered domain — build backlinks and content to establish SEO trust
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Informational: domain age. Newer domains may have lower trust signals in spam/security filters.
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice