Infrastructure - https://appsgolem.com BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

No CDN detected

A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN detected

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

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.

B

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 51.210.209.19 does not match any cert SAN: ns3179604.ip-51-210-209.eu

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.

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

No IPv6 (AAAA) records found

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

No IPv6 Support

About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B

TLS Certificate Expiry & Recommendations

76 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

76

days left

0d 30d 60d 90d+

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

B

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

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

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

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, 42 ms lookup

PASS

1 A records, 42 ms lookup

Resolves to 1 IPv4 address(es)

Got: 51.210.209.19

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns11.ovh.net, dns11.ovh.net

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 42 ms

Got: 42 ms

A	51.210.209.19
AAAA	—
CNAME	—
NS	ns11.ovh.net, dns11.ovh.net
MX	0 mail.appscyborg.com
TXT	SPF v=spf1 mx -all google-site-verification=fR1JDOpBG8Ig0HOrb0-4DU1FIjH7eIm0wLxIhwzARzA
CAA	Lookup not available with standard resolver

Resolved in 42 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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

DNSSEC

Signed and validating

PASS

Signed and validating

DNSSEC fully signed and chain validates (RSASHA256)

A+

Multi-Resolver DNS Speed

Mean 22ms across 3 resolvers (spread 45ms)

PASS

Mean 22ms across 3 resolvers (spread 45ms)

Cloudflare: 2ms

Got: 2ms via 1.1.1.1:53

Quad9: 18ms

Got: 18ms via 9.9.9.9:53

Google: 47ms

Got: 47ms via 8.8.8.8:53

A

Redirect Chain

1 redirect(s), 124 ms total

PASS

1 redirect(s), 124 ms total

Single redirect

Got: https://appsgolem.com → https://appsgolem.com/en/ (301)

https://appsgolem.com

61 ms · HTTP/1.1

301

https://appsgolem.com/en/

63 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://appsgolem.com	301	61 ms	HTTP/1.1	nginx
2	https://appsgolem.com/en/	200	63 ms	HTTP/1.1	nginx

See the visual redirect chain in the HTTP Probe tab →

A+

Crawlability

robots.txt present, sitemap with 1390 URLs

PASS

robots.txt present, sitemap with 1390 URLs

robots.txt is present

Got: 2230 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 1390 entries

robots.txt references sitemap

robots.txt 200 OK

Size 2230 B Sitemaps referenced 1 User-agents *, GPTBot, ChatGPT-User, OAI-SearchBot, Claude-Web, ByteSpider, PerplexityBot, Google-Extended, Amazonbot, cohere-ai, anthropic-ai, ClaudeBot, Applebot-Extended, Bingbot, FacebookBot, CCBot Blocking No — crawling allowed

User-agent: *

# Auth pages — thin/duplicate content across 38 locales, no SEO value
Disallow: /*/login/
Disallow: /*/register/
Disallow: /*/forgot/
Disallow: /*/logout/

# Account & payment pages — logged-in only, must not be indexed
Disallow: /*/account/
Disallow: /*/payment/

# Django i18n set-language POST endpoint (unprefixed, no content)
Disallow: /i18n/


# AI crawler directives — explicit allow for every documented LLM /
# AI-search bot. Default policy ("allow training too"): brand awareness
# in LLM weights > content protection. The product is a free-trial SaaS
# whose content is mostly tool-usage docs and comparison tables; having
# AppsGolem appear in ChatGPT / Claude / Perplexity training data is a
# discovery channel, not a leak risk. Inheritance from User-agent: *
# above already applies the same Disallow rules to every bot below.

# AI-search bots (power AI Overviews, ChatGPT web search, Perplexity, etc.)
User-agent: GPTBot
Allow: /

# ChatGPT-User is the fetch-on-behalf-of-a-user agent when ChatGPT looks
# something up mid-conversation. Distinct from GPTBot (which crawls for
# training / search index). Both agents inherit the Disallow rules from
# `User-agent: *` above so auth/account paths remain off-limits.
User-agent: ChatGPT-User
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Claude-Web
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Applebot-Extended
Allow: /

User-agent: Bingbot
Allow: /

# Amazonbot powers Alexa's answer engine + AI-adjacent Amazon products.
# Explicitly listed for parity with the other AI-search bots (was
# previously falling through to the wildcard rules — the 2026-07-02
# seo-geo audit flagged the inconsistency).
User-agent: Amazonbot
Allow: /

# AI training-data crawlers (Common Crawl, Anthropic training crawler).
# Explicitly allowed per the "allow training too" policy chosen on
# 2026-05-27. Reverse this to Disallow: / if the stance ever changes.
User-agent: CCBot
Allow: /

User-agent: anthropic-ai
Allow: /

User-agent: cohere-ai
Allow: /

User-agent: FacebookBot
Allow: /

User-agent: ByteSpider
Allow: /


Sitemap: https://appsgolem.com/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 1390 entries Valid XML Yes

Sample URLs:

A+

URL Variants

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

PASS

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

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

301https://www.appsgolem.com/

200https://appsgolem.com/

Preferred variant: non-www

HTTP → HTTPS

301http://appsgolem.com/ → https://appsgolem.com/

Consistent

A

Domain Intelligence

appsgolem.com — via OVH sas, 6 years, 11 months old, hosted on OVH

PASS

appsgolem.com — via OVH sas, 6 years, 11 months old, hosted on OVH

Domain expires in 55 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Oct 14, 2026

DNSSEC is enabled

Registrar: OVH sas

Registrar lock is NOT enabled

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.

Hosting: OVH

Got: AS16276

Domain expiry

49 days

October 14, 2026

SSL certificate

76 days

Issued by Let's Encrypt

Domain age

6 years, 11 months

Registered October 14, 2019

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

OVH

ASN AS16276

51.210.209.19

Registrar

OVH sas

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar OVH sas

Created October 14, 2019 (6 years, 11 months ago)

Expires October 14, 2026 (1 months)

Last Updated February 20, 2026

Name Servers dns11.ovh.net, ns11.ovh.net

DNSSEC Enabled

Hosting

IP Address 51.210.209.19

ASN AS16276 (OVH - OVH SAS, FR)

Provider OVH

Data source: rdap (0.1s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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.

Why this matters

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

A+

HTTP Probe Timing

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

PASS

DNS Lookup

33 ms

TCP Connect

6 ms

TLS Handshake

15 ms

Time to First Byte

74 ms

Total Time

74 ms

Connection waterfall

DNS Lookup 33 ms TCP Connect 6 ms TLS Handshake 15 ms Server Processing 19 ms Content Transfer 0 ms