Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/2 IPs match cert SANREVIEW
CMulti-Resolver DNS SpeedActionMean 123ms across 3 resolvers (spread 244ms)REVIEW
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
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: /wp-admin/
Allow: /wp-admin/admin-ajax.php
crawl-delay: 10
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations77 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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
CCDN & DeliveryActionAssets on Akamai (host consent.cookiebot.com, 3 assets); document served directly from originREVIEW
Asset hosts on a CDN
- consent.cookiebot.com — Akamai · assets: 3
Other asset hosts
- fonts.googleapis.com — assets: 10 · Google
- maps.googleapis.com — assets: 2 · below probe threshold
- consentcdn.cookiebot.com — assets: 1 · below probe threshold
The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records1 A records, 51 ms lookupPASS
| A | 217.26.60.154 |
| AAAA | 2a00:d70:0:b:2002:0:d91a:3c9a |
| CNAME | — |
| NS | ns3.hostpoint.ch, ns.hostpoint.ch, ns2.hostpoint.ch |
| MX | 10 mx1.mail.hostpoint.ch 10 mx2.mail.hostpoint.ch |
| TXT | SPF v=spf1 redirect=spf.mail.hostpoint.ch |
| 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
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Redirect ChainNo redirects — direct accessPASS
https://sandrasliving.swiss/casa-base/
628 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://sandrasliving.swiss/casa-base/ | 200 | 628 ms | HTTP/1.1 | Apache |
A+IPv6 ReadinessIPv6 reachable (29 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
Trailing Slash
HTTP → HTTPS
Consistent
A+Domain Intelligencesandrasliving.swiss — via Hostpoint, 3 months oldPASS
256 days
June 11, 2027
77 days
Issued by Let's Encrypt
3 months
Registered June 11, 2026
Not enabled
Protects against DNS spoofing
Unknown
2a00:d70:0:b:2002:0:d91a:3c9a
Hostpoint
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- 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.
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
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