Infrastructure - https://Psifos-participa.uchile.cl/psifos BeaverCheck Audit

B

DNS Records

2 A records, 34 ms lookup

REVIEW

2 A records, 34 ms lookup

Resolves to 2 IPv4 address(es)

Got: 104.20.38.219, 172.66.152.186

Has 2 IPv6 (AAAA) record(s)

Got: 2606:4700:10::ac42:98ba, 2606:4700:10::6814:26db

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: psifos-participa.uchile.cl.cdn.cloudflare.net

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution time: 34 ms

Got: 34 ms

A	104.20.38.219, 172.66.152.186
AAAA	2606:4700:10::ac42:98ba, 2606:4700:10::6814:26db
CNAME	psifos-participa.uchile.cl.cdn.cloudflare.net
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 34 ms

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

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

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)

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

B

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

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.

C

Reverse DNS

Action

0/4 IPs match cert SAN

REVIEW

0/4 IPs match cert SAN

PTR lookup failed for 104.20.38.219: lookup 104.20.38.219: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 172.66.152.186: lookup 172.66.152.186: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700:10::ac42:98ba: lookup 2606:4700:10::ac42:98ba: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700:10::6814:26db: lookup 2606:4700:10::6814:26db: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

C

Multi-Resolver DNS Speed

Action

Mean 216ms across 3 resolvers (spread 16ms)

REVIEW

Mean 216ms across 3 resolvers (spread 16ms)

Cloudflare: 209ms

Got: 209ms via 1.1.1.1:53

Quad9: 216ms

Got: 216ms via 9.9.9.9:53

Google: 225ms

Got: 225ms via 8.8.8.8:53

C

Crawlability

Action

robots.txt present, sitemap with 0 URLs

REVIEW

robots.txt present, sitemap with 0 URLs

robots.txt is present

Got: 67 bytes

sitemap.xml is present

sitemap.xml contains invalid XML

Search engines may not be able to parse the sitemap. Fix XML validation errors.

sitemap.xml is empty — no URLs found

An empty sitemap provides no value. Add <url> entries for your pages.

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

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.

Why this matters

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.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK

Size 67 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

# https://www.robotstxt.org/robotstxt.html
User-agent: *
Disallow:

sitemap.xml 200 OK

Type URL Set URLs 0 entries Valid XML No

B

HTTP Probe Timing

Total 889 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

238 ms

TCP Connect

16 ms

TLS Handshake

26 ms

Time to First Byte

889 ms

Total Time

889 ms

Connection waterfall

DNS Lookup 238 ms TCP Connect 16 ms TLS Handshake 26 ms Server Processing 609 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

66 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

66

days left

0d 30d 60d 90d+

Recommended actions

Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
Enable DNSSEC on your domain for DNS spoofing protection

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

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.

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://Psifos-participa.uchile.cl/psifos

https://Psifos-participa.uchile.cl/psifo...

650 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://Psifos-participa.uchile.cl/psifo...	200	650 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (18 ms)

PASS

IPv6 reachable (18 ms)

IPv6 is configured and reachable at 2606:4700:10::ac42:98ba, 2606:4700:10::6814:26db

Got: 18 ms connect

IPv6 Ready

AAAA Records 2606:4700:10::ac42:98ba, 2606:4700:10::6814:26db Connection Reachable (18 ms)

A

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

Trailing slash inconsistency — both versions serve content

Got: Both with/without trailing slash return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.Psifos-participa.uchile.cl/psifos

200https://Psifos-participa.uchile.cl/psifos

Trailing Slash

200https://Psifos-participa.uchile.cl/psifos/

200https://Psifos-participa.uchile.cl/psifos

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://Psifos-participa.uchile.cl/psifos → https://Psifos-participa.uchile.cl/psifos

Consistent

A

CDN & Delivery

Cloudflare (DYNAMIC)

PASS

Cloudflare (DYNAMIC)

Site is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: 9f994c97ba433d07-CDG

CDN cache status: DYNAMIC

CDN Detected: Cloudflare

Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f994c97ba433d07-CDG

A+

CDN Cache Observability

Cache state: DYNAMIC

PASS

Cache state: DYNAMIC

CDN cache state observable via 1 header(s)

Got: cf-cache-status=DYNAMIC

A+

Health Check Endpoint

Health endpoint at https://Psifos-participa.uchile.cl/health (HTTP 200)

PASS

Health endpoint at https://Psifos-participa.uchile.cl/health (HTTP 200)

Public health endpoint at https://Psifos-participa.uchile.cl/health

Got: https://Psifos-participa.uchile.cl/health

Domain Intelligence

Domain intelligence data not available

INFO

Domain intelligence data not available

RDAP and WHOIS lookup both failed