Infrastructure - https://www.jsrcgroup.com BeaverCheck Audit

D

CDN & Delivery

Action

No CDN (document or assets)

FIX

No CDN (document or assets)

Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

No CDN (document or assets)

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

B

DNS Records

1 A records, 340 ms lookup

REVIEW

1 A records, 340 ms lookup

Resolves to 1 IPv4 address(es)

Got: 104.196.192.123

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

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: jsrcgroup.com

2 nameserver(s) configured

Got: ns15.domaincontrol.com, ns16.domaincontrol.com

5 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (340 ms)

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

Got: 340 ms

A	104.196.192.123
AAAA	—
CNAME	jsrcgroup.com
NS	ns15.domaincontrol.com, ns16.domaincontrol.com
MX	1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx3.googlemail.com
TXT	facebook-domain-verification=rfsjac1ebru3gpxw2rgio61wgekzx1 google-site-verification=ojNJGqsZ678oQiuoiSirk0HeZLvU_Ts32kaxTeFYOlQ SPF v=spf1 include:_spf.google.com ~all
CAA	Lookup not available with standard resolver

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

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 104.196.192.123 does not match any cert SAN: 123.192.196.104.bc.googleusercontent.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.

B

Multi-Resolver DNS Speed

Mean 183ms across 3 resolvers (spread 103ms)

REVIEW

Mean 183ms across 3 resolvers (spread 103ms)

Google: 116ms

Got: 116ms via 8.8.8.8:53

Quad9: 215ms

Got: 215ms via 9.9.9.9:53

Cloudflare: 219ms

Got: 219ms via 1.1.1.1:53

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

HTTP Probe Timing

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

REVIEW

DNS Lookup

336 ms

TCP Connect

119 ms

TLS Handshake

241 ms

Time to First Byte

937 ms

Total Time

938 ms

Connection waterfall

DNS Lookup 336 ms TCP Connect 119 ms TLS Handshake 241 ms Server Processing 241 ms Content Transfer 1 ms

B

TLS Certificate Expiry & Recommendations

76 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

76

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.

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

CNAME does not point at a known takeover-able service

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://www.jsrcgroup.com

https://www.jsrcgroup.com

940 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.jsrcgroup.com	200	940 ms	HTTP/1.1	nginx

A+

Crawlability

robots.txt present, sitemap with 6 URLs

PASS

robots.txt present, sitemap with 6 URLs

robots.txt is present

Got: 82 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 6 entries

Sitemap index with 6 child sitemaps

robots.txt does not reference a sitemap

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 82 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Crawl-delay: 10

sitemap.xml 200 OK

Type Sitemap Index URLs 6 entries Valid XML Yes

Child Sitemaps:

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: www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.jsrcgroup.com/

301https://jsrcgroup.com/

Preferred variant: www

HTTP → HTTPS

301http://www.jsrcgroup.com/ → https://www.jsrcgroup.com/

Consistent

A+

Domain Intelligence

jsrcgroup.com — via GoDaddy.com, LLC, 6 years, 9 months old, hosted on Google Cloud

PASS

jsrcgroup.com — via GoDaddy.com, LLC, 6 years, 9 months old, hosted on Google Cloud

Domain registered until Jan 31, 2027 (4 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: GoDaddy.com, LLC

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: Google Cloud

Got: AS396982

Domain expiry

120 days

January 31, 2027

SSL certificate

76 days

Issued by Let's Encrypt

Domain age

6 years, 9 months

Registered January 31, 2020

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

104.196.192.123

Registrar

GoDaddy.com, LLC

Unlocked 2 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 GoDaddy.com, LLC

Created January 31, 2020 (6 years, 9 months ago)

Expires January 31, 2027 (4 months)

Last Updated February 1, 2026

Name Servers ns15.domaincontrol.com, ns16.domaincontrol.com

DNSSEC Not enabled

Hosting

IP Address 104.196.192.123

ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)

Provider Google Cloud

Data source: rdap (1.2s)

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+

CDN Cache Observability

Cache state: HIT:

PASS

Cache state: HIT:

CDN cache state observable via 1 header(s)

Got: x-cache=HIT: 2