Infrastructure - https://www.memorizza.com.br 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

DNS Records

1 A records, 424 ms lookup

REVIEW

1 A records, 424 ms lookup

Resolves to 1 IPv4 address(es)

Got: 56.126.55.34

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

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 is slow (424 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 424 ms

A	56.126.55.34
AAAA	—
CNAME	—
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 424 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

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)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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.

B

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 56.126.55.34 does not match any cert SAN: ec2-56-126-55-34.sa-east-1.compute.amazonaws.com

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

Multi-Resolver DNS Speed

Action

Mean 330ms across 3 resolvers (spread 231ms)

REVIEW

Mean 330ms across 3 resolvers (spread 231ms)

Google: 203ms

Got: 203ms via 8.8.8.8:53

Cloudflare: 354ms

Got: 354ms via 1.1.1.1:53

Quad9: 434ms

Got: 434ms via 9.9.9.9:53

High latency spread between resolvers: 231ms (min 203ms / max 434ms)

Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

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

URL Variants

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

REVIEW

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.memorizza.com.br/

200https://memorizza.com.br/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://www.memorizza.com.br/ → https://www.memorizza.com.br/

Consistent

B

HTTP Probe Timing

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

REVIEW

DNS Lookup

421 ms

TCP Connect

223 ms

TLS Handshake

227 ms

Time to First Byte

1.32 s

Total Time

1.32 s

Connection waterfall

DNS Lookup 421 ms TCP Connect 223 ms TLS Handshake 227 ms Server Processing 446 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

79 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

79

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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.memorizza.com.br

https://www.memorizza.com.br

885 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.memorizza.com.br	200	885 ms	HTTP/1.1	nginx/1.30.4

A+

Crawlability

robots.txt present, sitemap with 6 URLs

PASS

robots.txt present, sitemap with 6 URLs

robots.txt is present

Got: 659 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 6 entries

robots.txt references sitemap

robots.txt 200 OK

Size 659 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *
Allow: /
Disallow: /dashboard
Disallow: /admin
Disallow: /library
Disallow: /knowledge
Disallow: /flashcards
Disallow: /questions
Disallow: /reviews
Disallow: /highlights
Disallow: /ai
Disallow: /marketplace
Disallow: /community
Disallow: /teacher
Disallow: /stats
Disallow: /estatisticas
Disallow: /profile
Disallow: /meusdados
Disallow: /achievements
Disallow: /ajuda
Disallow: /learning-pack
Disallow: /social
Disallow: /group-invite
Disallow: /teacher-invite
Disallow: /reset-password
Disallow: /forgot-password
Disallow: /verify-email
Disallow: /login/2fa
Disallow: /auth/
Disallow: /api/

Sitemap: https://www.memorizza.com.br/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 6 entries Valid XML Yes

Sample URLs:

A+

Domain Intelligence

memorizza.com.br — 10 days old, hosted on AWS

PASS

memorizza.com.br — 10 days old, hosted on AWS

Domain registered until Aug 19, 2027 (11 months remaining)

Domain is only 10 days old

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.

Got: Registered Aug 19, 2026

DNSSEC is enabled

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: AWS

Got: AS16509

Domain expiry

354 days

August 19, 2027

SSL certificate

79 days

Issued by Let's Encrypt

Domain age

10 days

Registered August 19, 2026

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

56.126.55.34

Registrar

Registrar unknown

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Newly registered domain — build backlinks and content to establish SEO trust
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar

Created August 19, 2026 (10 days ago)

Expires August 19, 2027 (11 months)

Last Updated August 19, 2026

Name Servers b.sec.dns.br, c.sec.dns.br

DNSSEC Enabled

Registrant Alexandre Martins

Hosting

IP Address 56.126.55.34

ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (1.1s)

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.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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