Infrastructure - https://Juno-innovations.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 13.227.173.92 does not match any cert SAN: server-13-227-173-92.cdg54.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 13.227.173.56 does not match any cert SAN: server-13-227-173-56.cdg54.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 13.227.173.4 does not match any cert SAN: server-13-227-173-4.cdg54.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 13.227.173.116 does not match any cert SAN: server-13-227-173-116.cdg54.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

TLS Certificate Expiry & Recommendations

126 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

126

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+

DNS Records

4 A records, 47 ms lookup

PASS

4 A records, 47 ms lookup

Resolves to 4 IPv4 address(es)

Got: 13.227.173.92, 13.227.173.56, 13.227.173.4, 13.227.173.116

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-787.awsdns-34.net, ns-1135.awsdns-13.org, ns-212.awsdns-26.com, ns-1579.awsdns-05.co.uk

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: 47 ms

Got: 47 ms

A	13.227.173.92, 13.227.173.56, 13.227.173.4, 13.227.173.116
AAAA	—
CNAME	—
NS	ns-787.awsdns-34.net, ns-1135.awsdns-13.org, ns-212.awsdns-26.com, ns-1579.awsdns-05.co.uk
MX	1 smtp.google.com
TXT	google-site-verification=BR6Hlr1YSk8rf-p7NMZ2ZUdhMkwm1g-oI1pDL7M9QLc
CAA	Lookup not available with standard resolver

Resolved in 47 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 26ms across 3 resolvers (spread 22ms)

PASS

Mean 26ms across 3 resolvers (spread 22ms)

Quad9: 14ms

Got: 14ms via 9.9.9.9:53

Cloudflare: 28ms

Got: 28ms via 1.1.1.1:53

Google: 36ms

Got: 36ms via 8.8.8.8:53

A

Redirect Chain

1 redirect(s), 337 ms total

PASS

1 redirect(s), 337 ms total

Single redirect

Got: https://Juno-innovations.com → https://www.juno-innovations.com/ (302)

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://Juno-innovations.com

https://Juno-innovations.com

157 ms · HTTP/1.1

302

https://www.juno-innovations.com/

180 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://Juno-innovations.com	302	157 ms	HTTP/1.1
2	https://www.juno-innovations.com/	200	180 ms	HTTP/1.1	Framer/a338d3d

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+

Crawlability

robots.txt present, sitemap with 28 URLs

PASS

robots.txt present, sitemap with 28 URLs

robots.txt is present

Got: 2564 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 28 entries

robots.txt references sitemap

robots.txt 200 OK

Size 2564 B Sitemaps referenced 1 User-agents Googlebot, DuckDuckBot, PerplexityBot, anthropic-ai, Bytespider, *, OAI-SearchBot, ChatGPT-User, Applebot, Bingbot, Slurp, GPTBot, ClaudeBot, Google-Extended, Meta-ExternalAgent, PetalBot Blocking No — crawling allowed

# robots.txt — juno-innovations.com
# Last updated: April 2026

# -------------------------------------------------------
# Standard crawlers — full access to public content
# -------------------------------------------------------

User-agent: Googlebot
Allow: /

User-agent: Bingbot
Allow: /

User-agent: Slurp
Allow: /

User-agent: DuckDuckBot
Allow: /

# -------------------------------------------------------
# AI training crawlers — allow public content,
# block restricted and noindexed paths
# -------------------------------------------------------

User-agent: GPTBot
Allow: /
Allow: /llms.txt
Disallow: /contact/beta
Disallow: /blog
Disallow: /team
Disallow: /story
Disallow: /press
Disallow: /community
Disallow: /faq

User-agent: OAI-SearchBot
Allow: /
Allow: /llms.txt
Disallow: /contact/beta
Disallow: /blog
Disallow: /team
Disallow: /story
Disallow: /press
Disallow: /community
Disallow: /faq

User-agent: ChatGPT-User
Allow: /
Allow: /llms.txt
Disallow: /contact/beta

User-agent: PerplexityBot
Allow: /
Allow: /llms.txt
Disallow: /contact/beta
Disallow: /blog
Disallow: /team
Disallow: /story
Disallow: /press
Disallow: /community
Disallow: /faq

User-agent: anthropic-ai
Allow: /
Allow: /llms.txt
Disallow: /contact/beta
Disallow: /blog
Disallow: /team
Disallow: /story
Disallow: /press
Disallow: /community
Disallow: /faq

User-agent: ClaudeBot
Allow: /
Allow: /llms.txt
Disallow: /contact/beta
Disallow: /blog
Disallow: /team
Disallow: /story
Disallow: /press
Disallow: /community
Disallow: /faq

# Google AI training opt-out (separate from Googlebot search crawl)
# Set to Allow to remain eligible for Google AI Overviews and AI Mode citations.
# Change to Disallow: / if you decide to opt out of Google AI training.
User-agent: Google-Extended
Allow: /

# Meta AI crawler
User-agent: Meta-ExternalAgent
Allow: /
Disallow: /contact/beta

# Apple Applebot (Siri, Spotlight)
User-agent: Applebot
Allow: /

# Common AI agent crawlers
User-agent: Bytespider
Disallow: /

User-agent: PetalBot
Allow: /

# -------------------------------------------------------
# Default: all other crawlers get full access
# -------------------------------------------------------

User-agent: *
Allow: /
Disallow: /contact/beta

# -------------------------------------------------------
# Sitemap and AI context file
# -------------------------------------------------------

Sitemap: https://juno-innovations.com/sitemap.xml

# AI context file (llms.txt spec — answer.ai/posts/2024-09-03-llmstxt.html)
# LLMs-txt: https://juno-innovations.com/llms.txt

sitemap.xml 200 OK

Type URL Set URLs 28 entries Valid XML Yes

Sample URLs:

A+

URL Variants

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

PASS

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

HTTP correctly 301-redirects to HTTPS

www / non-www

404https://www.Juno-innovations.com/

200https://Juno-innovations.com/

HTTP → HTTPS

301http://Juno-innovations.com/ → https://juno-innovations.com/

Consistent

A+

Domain Intelligence

Juno-innovations.com — via Amazon Registrar, Inc., 1 years, 11 months old, hosted on AWS

PASS

Juno-innovations.com — via Amazon Registrar, Inc., 1 years, 11 months old, hosted on AWS

Domain registered until Jun 14, 2027 (1 years, 1 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

395 days

June 14, 2027

SSL certificate

126 days

Issued by Amazon

Domain age

1 years, 11 months

Registered June 14, 2024

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.227.173.92

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 June 14, 2024 (1 years, 11 months ago)

Expires June 14, 2027 (1 years, 1 months)

Last Updated May 10, 2026

Name Servers ns-1135.awsdns-13.org, ns-1579.awsdns-05.co.uk, ns-212.awsdns-26.com, ns-787.awsdns-34.net

DNSSEC Not enabled

Hosting

IP Address 13.227.173.92

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

Provider AWS

Data source: rdap (0.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+

HTTP Probe Timing

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

PASS

DNS Lookup

36 ms

TCP Connect

17 ms

TLS Handshake

23 ms

Time to First Byte

199 ms

Total Time

199 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 124 ms Content Transfer 0 ms

A

CDN & Delivery

AWS CloudFront (Miss from cloudfront)

PASS

AWS CloudFront (Miss from cloudfront)

Site is served via AWS CloudFront CDN (edge: CDG54-P2)

Got: x-amz-cf-id: Tg543Pl6Y_wTMXdr4tPDcVjgufgL8uTnhh_RkAUkciDJmPNfpYbNyw==

CDN cache status: Miss from cloudfront

CDN Detected: AWS CloudFront

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

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