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

F

HTTP Probe Timing

Action

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

FIX

DNS Lookup

44 ms

TCP Connect

155 ms

TLS Handshake

167 ms

Time to First Byte

7.65 s

Total Time

7.65 s

Connection waterfall

DNS Lookup 44 ms TCP Connect 155 ms TLS Handshake 167 ms Server Processing 7.28 s Content Transfer 0 ms

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

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

REVIEW

0/2 IPs match cert SAN

PTR lookup failed for 185.212.71.184: lookup 185.212.71.184: 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.

PTR lookup failed for 2a02:4780:b:748:0:1ff7:607c:4: lookup 2a02:4780:b:748:0:1ff7:607c:4: 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), 1005 ms total

REVIEW

1 redirect(s), 1005 ms total

Single redirect

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

WWW normalization redirect

Redirect overhead: 1005 ms total

Got: 1005 ms

https://www.oneou.com

520 ms · HTTP/1.1

301

https://oneou.com/

485 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.oneou.com	301	520 ms	HTTP/1.1	LiteSpeed
2	https://oneou.com/	200	485 ms	HTTP/1.1	LiteSpeed

See the visual redirect chain in the HTTP Probe tab →

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 301-redirects to HTTPS

www / non-www

200https://www.oneou.com/

200https://oneou.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B

TLS Certificate Expiry & Recommendations

71 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

71

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

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

A

DNS Records

1 A records, 49 ms lookup

PASS

1 A records, 49 ms lookup

Resolves to 1 IPv4 address(es)

Got: 185.212.71.184

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2a02:4780:b:748:0:1ff7:607c:4

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

2 nameserver(s) configured

Got: aurora.dns-parking.com, nebula.dns-parking.com

2 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 49 ms

Got: 49 ms

A	185.212.71.184
AAAA	2a02:4780:b:748:0:1ff7:607c:4
CNAME	oneou.com
NS	aurora.dns-parking.com, nebula.dns-parking.com
MX	5 mx1.hostinger.com 10 mx2.hostinger.com
TXT	SPF v=spf1 include:_spf.mail.hostinger.com ~all
CAA	Lookup not available with standard resolver

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

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+

Multi-Resolver DNS Speed

Mean 46ms across 3 resolvers (spread 46ms)

PASS

Mean 46ms across 3 resolvers (spread 46ms)

Google: 30ms

Got: 30ms via 8.8.8.8:53

Cloudflare: 32ms

Got: 32ms via 1.1.1.1:53

Quad9: 76ms

Got: 76ms via 9.9.9.9:53

A+

IPv6 Readiness

IPv6 reachable (154 ms)

PASS

IPv6 reachable (154 ms)

IPv6 is configured and reachable at 2a02:4780:b:748:0:1ff7:607c:4

Got: 154 ms connect

IPv6 Ready

AAAA Records 2a02:4780:b:748:0:1ff7:607c:4 Connection Reachable (154 ms)

A+

Crawlability

robots.txt present, sitemap with 6 URLs

PASS

robots.txt present, sitemap with 6 URLs

robots.txt is present

Got: 235 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 6 entries

Sitemap index with 6 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 235 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed

User-agent: *

Disallow: /wp-admin/

Allow: /wp-admin/admin-ajax.php

Disallow: /author/

Disallow: /cart/

Disallow: /my-account/

Disallow: /checkout/


Sitemap: https://oneou.com/sitemap.xml

Sitemap: https://oneou.com/sitemap.rss

sitemap.xml 200 OK

Type Sitemap Index URLs 6 entries Valid XML Yes

Child Sitemaps:

A

Domain Intelligence

oneou.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 9 years old

PASS

oneou.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 9 years old

Domain expires in 43 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Aug 3, 2026

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: Alibaba Cloud Computing (Beijing) Co., Ltd.

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.

Domain expiry

22 days

August 3, 2026

SSL certificate

71 days

Issued by Let's Encrypt

Domain age

9 years

Registered August 3, 2017

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:4780:b:748:0:1ff7:607c:4

Registrar

Alibaba Cloud Computing (Beijing) Co., Ltd.

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Alibaba Cloud Computing (Beijing) Co., Ltd.

Created August 3, 2017 (9 years ago)

Expires August 3, 2026 (1 months)

Last Updated June 19, 2026

Name Servers aurora.dns-parking.com, nebula.dns-parking.com

DNSSEC Not enabled

Hosting

IP Address 2a02:4780:b:748:0:1ff7:607c:4

Data source: rdap (0.2s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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