Infrastructure - https://quarterchart.com BeaverCheck Audit

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/4 IPs match cert SAN

REVIEW

0/4 IPs match cert SAN

PTR for 18.244.28.62 does not match any cert SAN: server-18-244-28-62.cdg52.r.cloudfront.net

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.

PTR for 18.244.28.91 does not match any cert SAN: server-18-244-28-91.cdg52.r.cloudfront.net

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.

PTR for 18.244.28.76 does not match any cert SAN: server-18-244-28-76.cdg52.r.cloudfront.net

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.

PTR for 18.244.28.77 does not match any cert SAN: server-18-244-28-77.cdg52.r.cloudfront.net

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

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.quarterchart.com/

200https://quarterchart.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B

TLS Certificate Expiry & Recommendations

72 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

72

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

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+

DNS Records

4 A records, 43 ms lookup

PASS

4 A records, 43 ms lookup

Resolves to 4 IPv4 address(es)

Got: 18.244.28.62, 18.244.28.91, 18.244.28.76, 18.244.28.77

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-1431.awsdns-50.org, ns-1686.awsdns-18.co.uk, ns-334.awsdns-41.com, ns-984.awsdns-59.net

1 mail exchanger(s) configured

No SPF record found in TXT records

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

DNS resolution time: 43 ms

Got: 43 ms

A	18.244.28.62, 18.244.28.91, 18.244.28.76, 18.244.28.77
AAAA	—
CNAME	—
NS	ns-1431.awsdns-50.org, ns-1686.awsdns-18.co.uk, ns-334.awsdns-41.com, ns-984.awsdns-59.net
MX	10 inbound-smtp.us-east-1.amazonaws.com
TXT	google-site-verification=b-R7LwyGvoFUo-nln6ZhuZ4_0Ma3FnMjkvS6U5PMDHc
CAA	Lookup not available with standard resolver

Resolved in 43 ms

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)

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 19ms across 3 resolvers (spread 38ms)

PASS

Mean 19ms across 3 resolvers (spread 38ms)

Quad9: 1ms

Got: 1ms via 9.9.9.9:53

Cloudflare: 18ms

Got: 18ms via 1.1.1.1:53

Google: 39ms

Got: 39ms via 8.8.8.8:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://quarterchart.com

https://quarterchart.com

525 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://quarterchart.com	200	525 ms	HTTP/1.1	nginx/1.18.0 (Ubuntu)

A+

Crawlability

robots.txt present, sitemap with 7 URLs

PASS

robots.txt present, sitemap with 7 URLs

robots.txt is present

Got: 575 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 7 entries

Sitemap index with 7 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

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

User-agent: *
Disallow: /admin/
Disallow: /api/
Disallow: /accounts/password/
# /static/frontend/ (JS/CSS bundles) must stay crawlable: Googlebot needs to
# fetch them to render the React app. Blocking them = Google only sees the
# SSR skeleton (measured 2026-07: /earnings ranked pos 24 for "earnings calendar").
Allow: /static/frontend/
Allow: /static/images/
Allow: /static/css/

# Sitemap location
Sitemap: https://quarterchart.com/sitemap.xml

# High-priority pages for faster indexing
# Homepage: https://quarterchart.com/
# Earnings: https://quarterchart.com/earnings

sitemap.xml 200 OK

Type Sitemap Index URLs 7 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

quarterchart.com — via Amazon Registrar, Inc., 3 years, 7 months old, hosted on AWS

PASS

quarterchart.com — via Amazon Registrar, Inc., 3 years, 7 months old, hosted on AWS

Domain registered until Mar 3, 2027 (5 months remaining)

DNSSEC is not enabled

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Registrar: Amazon Registrar, Inc.

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

151 days

March 3, 2027

SSL certificate

72 days

Issued by Amazon

Domain age

3 years, 7 months

Registered March 3, 2023

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

18.244.28.76

Registrar

Amazon Registrar, Inc.

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Amazon Registrar, Inc.

Created March 3, 2023 (3 years, 7 months ago)

Expires March 3, 2027 (5 months)

Last Updated January 27, 2026

Name Servers ns-1431.awsdns-50.org, ns-1686.awsdns-18.co.uk, ns-334.awsdns-41.com, ns-984.awsdns-59.net

DNSSEC Not enabled

Hosting

IP Address 18.244.28.76

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

Provider AWS

Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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 578 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

37 ms

TCP Connect

16 ms

TLS Handshake

20 ms

Time to First Byte

491 ms

Total Time

579 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 16 ms TLS Handshake 20 ms Server Processing 418 ms Content Transfer 88 ms

A

CDN & Delivery

Document on AWS CloudFront; assets also on Cloudflare

PASS

Document on AWS CloudFront; assets also on Cloudflare

Document is served via AWS CloudFront CDN (edge: CDG52-P5)

Got: x-amz-cf-id: 08STPeLUu6N74rH3jBvw49nVHy7YvXgKlkktd1s10WMACwT0yi9SWg==

CDN cache status: Miss from cloudfront

Assets on AWS CloudFront: d10ljhp4s33jqi.cloudfront.net (assets: 140), cache Hit from cloudfront

Got: delegation d10ljhp4s33jqi.cloudfront.net

Assets on Cloudflare: us-assets.i.posthog.com (assets: 5), cache HIT

Got: cf-ray: a43a6f9d383d9dae-CDG

Document served via CDN: AWS CloudFront

Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: 08STPeLUu6N74rH3jBvw49nVHy7YvXgKlkktd1s10WMACwT0yi9SWg==

Asset hosts on a CDN

d10ljhp4s33jqi.cloudfront.net — AWS CloudFront · assets: 140 · Cache Status: Hit from cloudfront
us-assets.i.posthog.com — Cloudflare · assets: 5 · Cache Status: HIT

Other asset hosts

fonts.googleapis.com — assets: 4 · Google
www.googletagmanager.com — assets: 1 · below probe threshold

A+

CDN Cache Observability

Cache state: MISS

PASS

Cache state: MISS

CDN cache state observable via 1 header(s)

Got: x-cache=Miss from cloudfront

A+

Health Check Endpoint

Health endpoint at https://quarterchart.com/healthz (HTTP 200)

PASS

Health endpoint at https://quarterchart.com/healthz (HTTP 200)

Public health endpoint at https://quarterchart.com/healthz

Got: https://quarterchart.com/healthz