Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
User-agent: *
Disallow: /x/
Disallow: /std/
Disallow: /add_module
BHTTP Probe TimingTotal 1285 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations80 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records1 A records, 74 ms lookupPASS
| A | 69.67.170.170 |
| AAAA | 2602:f70f::1 |
| CNAME | — |
| NS | ns-cloud-c2.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c4.googledomains.com, ns-cloud-c3.googledomains.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com 15 mxcbid3fa2xdcnxzi54yx7s24zg7mxdlgiyz27okxampj5rpxxva.mx-verification.google.com |
| TXT | DirectFedPassiveSignInUri=https://accounts.google.com/o/saml2/idp?idpid=C00i63oz... google-site-verification=cKm9DNhH8cPJM4iDzag5nutN_-rMmVtNrZTS1eagrc0 MS=ms55636499 google-site-verification=mK20W9JDnIjbXLAFnqJmnnBB_iP85coianQ22im3z2g rippling-domain-verification=41aba443cffed29e DirectFedAuthUrl=https://accounts.google.com/o/saml2/idp?idpid=C00i63oz4 slack-domain-verification=t1y5dJlFS0h8GhBl7rJNtrTPxJC1GucfYSkyzVZi SPF v=spf1 include:_spf.google.com include:amazonses.com include:spf.mailjet.com ~al... google-site-verification=wYdcDfJ1JWHCGhiLfzLCb81tOs_JnyCnqiJkjMM2Dy8 stripe-verification=49e875edde4b54944b80255bb7b0af6fb0df6526c57effa6e5c8c4a7a152... |
| 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
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Redirect ChainNo redirects — direct accessPASS
https://deno.com
660 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://deno.com | 200 | 660 ms | HTTP/1.1 | deployd |
A+IPv6 ReadinessIPv6 reachable (209 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencedeno.com — via NameCheap, Inc., 27 years, 5 months oldPASS
1336 days
March 9, 2030
80 days
Issued by Let's Encrypt
27 years, 5 months
Registered March 9, 1999
Not enabled
Protects against DNS spoofing
Unknown
2602:f70f::1
NameCheap, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033