Skip to content
https://www.oracles.ch

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
8
PASS
7
INFO
1
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 8 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

C
DNSSEC
Action
Zone signed but parent has no DS record
REVIEW
Zone signed but parent has no DS record
Warning::
DNSSEC keys published but parent zone has no DS record
The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 80.74.149.177 does not match any cert SAN: miranda.kreativmedia.ch
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a00:1128:0:157::32 does not match any cert SAN: miranda.kreativmedia.ch
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
Multi-Resolver DNS Speed
Mean 94ms across 3 resolvers (spread 114ms)
REVIEW
Mean 94ms across 3 resolvers (spread 114ms)
Info::
Google: 35ms
Got: 35ms via 8.8.8.8:53
Info::
Cloudflare: 100ms
Got: 100ms via 1.1.1.1:53
Info::
Quad9: 149ms
Got: 149ms via 9.9.9.9:53
B
TLS Certificate Expiry & Recommendations
43 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

43
days left
0d 30d 60d 90d+

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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
1 A records, 66 ms lookup
PASS
1 A records, 66 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 80.74.149.177
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a00:1128:0:157::32
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: oracles.ch
Info::
2 nameserver(s) configured
Got: ns49.kreativmedia.ch, ns50.kreativmedia.ch
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 66 ms
Got: 66 ms
A80.74.149.177
AAAA2a00:1128:0:157::32
CNAMEoracles.ch
NSns49.kreativmedia.ch, ns50.kreativmedia.ch
MX
10 mail.oracles.ch
TXT
SPF v=spf1 include:_spf.kreativmedia.ch +mx +a -all
CAALookup not available with standard resolver
Resolved in 66 ms

Multiple A records provide failover if one server goes down.

Why this matters

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 CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.oracles.ch

https://www.oracles.ch

103 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.oracles.ch200103 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (39 ms)
PASS
IPv6 reachable (39 ms)
Info::
IPv6 is configured and reachable at 2a00:1128:0:157::32
Got: 39 ms connect
IPv6 Ready
AAAA Records 2a00:1128:0:157::32 Connection Reachable (39 ms)
A+
Crawlability
robots.txt present, sitemap with 1034 URLs
PASS
robots.txt present, sitemap with 1034 URLs
Info::
robots.txt is present
Got: 139 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1034 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 139 B Sitemaps referenced 1 User-agents Mediapartners-Google, * Blocking No — crawling allowed
User-agent: *
Disallow: /erreur/
Disallow: /stat/

Sitemap: https://www.oracles.ch/sitemap.xml

User-agent: Mediapartners-Google 
Disallow:
sitemap.xml 200 OK
Type URL Set URLs 1034 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.oracles.ch/
301https://oracles.ch/

Preferred variant: www

HTTP → HTTPS

301http://www.oracles.ch/ → https://www.oracles.ch/

Consistent

A+
HTTP Probe Timing
Total 184 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
74 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
29 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
38 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
184 ms
Total Time Total request time from DNS lookup through full response.
184 ms

Connection waterfall

DNS Lookup 74 ms TCP Connect 29 ms TLS Handshake 38 ms Server Processing 44 ms Content Transfer 0 ms
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback