Infrastructure - https://unifycloud.com BeaverCheck Audit

D

URL Variants

Action

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

FIX

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 version does not redirect to HTTPS

Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

200https://www.unifycloud.com/

200https://unifycloud.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

http://unifycloud.com/

HTTP version does not redirect to HTTPS

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.

Got: document origin: Microsoft Azure

No CDN (document or assets)

Document origin Microsoft Azure

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

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.

C

Reverse DNS

Action

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR lookup failed for 134.33.247.57: lookup 134.33.247.57: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

B

Redirect Chain

1 redirect(s), 1183 ms total

REVIEW

1 redirect(s), 1183 ms total

Single redirect

Got: https://unifycloud.com → https://www.unifycloud.com/ (301)

WWW normalization redirect

Redirect overhead: 1183 ms total

Got: 1183 ms

https://unifycloud.com

292 ms · HTTP/1.1

301

https://www.unifycloud.com/

891 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://unifycloud.com	301	292 ms	HTTP/1.1	Microsoft-Azure-Application-Gateway/v2
2	https://www.unifycloud.com/	200	891 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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

31 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

31

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

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: connection error, /healthz: connection error, /ping: connection error, /status: connection error.

A+

DNS Records

1 A records, 112 ms lookup

PASS

1 A records, 112 ms lookup

Resolves to 1 IPv4 address(es)

Got: 134.33.247.57

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns41.domaincontrol.com, ns42.domaincontrol.com, ns2-34.azure-dns.net, ns1-34.azure-dns.com

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 112 ms

Got: 112 ms

A	134.33.247.57
AAAA	—
CNAME	—
NS	ns41.domaincontrol.com, ns42.domaincontrol.com, ns2-34.azure-dns.net, ns1-34.azure-dns.com
MX	0 unifycloud-com.mail.protection.outlook.com
TXT	unifycloud-prod.azurewebsites.net google-site-verification=hgaEUBgAyKFwoWJnjZopA5fyJV8kuTX-h2HpGhKk5oQ SPF v=spf1 include:spf.protection.outlook.com -all 9t131mmk8buj26emlbue8op706
CAA	Lookup not available with standard resolver

Resolved in 112 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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A

Multi-Resolver DNS Speed

Mean 46ms across 3 resolvers (spread 57ms)

PASS

Mean 46ms across 3 resolvers (spread 57ms)

Cloudflare: 25ms

Got: 25ms via 1.1.1.1:53

Google: 32ms

Got: 32ms via 8.8.8.8:53

Quad9: 82ms

Got: 82ms via 9.9.9.9:53

A+

Crawlability

robots.txt present, sitemap with 131 URLs

PASS

robots.txt present, sitemap with 131 URLs

robots.txt is present

Got: 514 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 131 entries

robots.txt references sitemap

robots.txt 200 OK

Size 514 B Sitemaps referenced 1 User-agents Meta-ExternalAgent, GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Perplexity-User, CCBot, *, Claude-Web, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, Amazonbot Blocking No — crawling allowed

User-Agent: *
Allow: /
Disallow: /api/
Disallow: /styleguide

User-Agent: GPTBot
User-Agent: OAI-SearchBot
User-Agent: ChatGPT-User
User-Agent: ClaudeBot
User-Agent: Claude-Web
User-Agent: anthropic-ai
User-Agent: PerplexityBot
User-Agent: Perplexity-User
User-Agent: Google-Extended
User-Agent: Applebot-Extended
User-Agent: Amazonbot
User-Agent: Meta-ExternalAgent
User-Agent: CCBot
Allow: /
Disallow: /api/
Disallow: /styleguide

Host: https://www.unifycloud.com
Sitemap: https://www.unifycloud.com/sitemap.xml

sitemap.xml 200 OK

Type URL Set URLs 131 entries Valid XML Yes

Sample URLs:

A+

Domain Intelligence

unifycloud.com — via GoDaddy.com, LLC, 17 years, 6 months old, hosted on Microsoft Azure

PASS

unifycloud.com — via GoDaddy.com, LLC, 17 years, 6 months old, hosted on Microsoft Azure

Domain registered until Jun 23, 2027 (9 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: Microsoft Azure

Got: AS8075

Domain expiry

273 days

June 23, 2027

SSL certificate

31 days

Issued by GoDaddy.com, Inc.

Domain age

17 years, 6 months

Registered June 23, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

134.33.247.57

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 June 23, 2009 (17 years, 6 months ago)

Expires June 23, 2027 (9 months)

Last Updated June 24, 2025

Name Servers ns41.domaincontrol.com, ns42.domaincontrol.com

DNSSEC Not enabled

Hosting

IP Address 134.33.247.57

ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)

Provider Microsoft Azure

Data source: rdap (0.4s)

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

PASS

DNS Lookup

35 ms

TCP Connect

99 ms

TLS Handshake

101 ms

Time to First Byte

333 ms

Total Time

333 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 99 ms TLS Handshake 101 ms Server Processing 99 ms Content Transfer 0 ms