Skip to content
https://appsgolem.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
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.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
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
Crawlability
robots.txt present, sitemap with 1129 URLs
REVIEW
robots.txt present, sitemap with 1129 URLs
Info::
robots.txt is present
Got: 411 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Info::
sitemap.xml contains 1129 entries
Info::
robots.txt references 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

robots.txt 200 OK
Size 411 B Sitemaps referenced 1 User-agents * 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/

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

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

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 45 ms lookup
PASS
1 A records, 45 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 51.210.209.19
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns11.ovh.net, ns11.ovh.net
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 45 ms
Got: 45 ms
A51.210.209.19
AAAA
CNAME
NSdns11.ovh.net, ns11.ovh.net
MX
0 mail.appscyborg.com
TXT
google-site-verification=fR1JDOpBG8Ig0HOrb0-4DU1FIjH7eIm0wLxIhwzARzA
SPF v=spf1 mx -all
CAALookup not available with standard resolver
Resolved in 45 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 122 ms total
PASS
1 redirect(s), 122 ms total
Info::
Single redirect
Got: https://appsgolem.com → https://appsgolem.com/en/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://appsgolem.com

https://appsgolem.com

68 ms · HTTP/1.1

302

https://appsgolem.com/en/

54 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://appsgolem.com30268 msHTTP/1.1nginx
2https://appsgolem.com/en/20054 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

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, 7 months old, hosted on OVH
PASS
appsgolem.com — via OVH sas, 6 years, 7 months old, hosted on OVH
Info::
Domain registered until Oct 14, 2026 (5 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: OVH sas
Warning::
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.
Info::
Hosting: OVH
Got: AS16276
Domain expiry

94 days

October 14, 2026

SSL certificate

76 days

Issued by Let's Encrypt

Domain age

6 years, 7 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar OVH sas
Created October 14, 2019 (6 years, 7 months ago)
Expires October 14, 2026 (5 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, FR)
Provider OVH
Data source: rdap (0.3s)

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 114 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
20 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
114 ms
Total Time Total request time from DNS lookup through full response.
114 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 20 ms TLS Handshake 22 ms Server Processing 25 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback