Infrastructure - https://otomedis.my.id BeaverCheck Audit

D

Multi-Resolver DNS Speed

Action

Mean 180ms across 3 resolvers (spread 319ms)

FIX

Mean 180ms across 3 resolvers (spread 319ms)

Google: 20ms

Got: 20ms via 8.8.8.8:53

Quad9: 181ms

Got: 181ms via 9.9.9.9:53

Cloudflare: 339ms

Got: 339ms via 1.1.1.1:53

High latency spread between resolvers: 319ms (min 20ms / max 339ms)

Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

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 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.otomedis.my.id/

200https://otomedis.my.id/

Inconsistent — duplicate content risk

HTTP → HTTPS

200http://otomedis.my.id/

HTTP version does not redirect to HTTPS

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.

B

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 195.88.211.25 does not match any cert SAN: mten.kencang.id

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

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B

HTTP Probe Timing

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

REVIEW

DNS Lookup

285 ms

TCP Connect

184 ms

TLS Handshake

190 ms

Time to First Byte

849 ms

Total Time

850 ms

Connection waterfall

DNS Lookup 285 ms TCP Connect 184 ms TLS Handshake 190 ms Server Processing 190 ms Content Transfer 1 ms

B

TLS Certificate Expiry & Recommendations

51 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

51

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

A

DNS Records

1 A records, 328 ms lookup

PASS

1 A records, 328 ms lookup

Resolves to 1 IPv4 address(es)

Got: 195.88.211.25

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: srv2.arenhost.com, srv1.arenhost.com

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (328 ms)

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

Got: 328 ms

A	195.88.211.25
AAAA	—
CNAME	—
NS	srv2.arenhost.com, srv1.arenhost.com
MX	0 otomedis.my.id
TXT	SPF v=spf1 +a +mx +ip4:195.88.211.25 ~all
CAA	Lookup not available with standard resolver

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

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

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://otomedis.my.id

https://otomedis.my.id

565 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://otomedis.my.id	200	565 ms	HTTP/1.1

A+

Domain Intelligence

otomedis.my.id — via PT JC Indonesia, 1 months old, hosted on ArenHost - Hadi Santosa, ID

PASS

otomedis.my.id — via PT JC Indonesia, 1 months old, hosted on ArenHost - Hadi Santosa, ID

Domain registered until Jun 29, 2027 (10 months remaining)

Domain is only 1 months old

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Got: Registered Jun 29, 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: PT JC Indonesia

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: ArenHost - Hadi Santosa, ID

Got: AS214882

Domain expiry

325 days

June 29, 2027

SSL certificate

51 days

Issued by Let's Encrypt

Domain age

1 months

Registered June 29, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

ArenHost - Hadi Santosa, ID

ASN AS214882

195.88.211.25

Registrar

PT JC Indonesia

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
Newly registered domain — build backlinks and content to establish SEO trust
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar PT JC Indonesia

Created June 29, 2026 (1 months ago)

Expires June 29, 2027 (10 months)

Last Updated June 29, 2026

Name Servers srv1.arenhost.com, srv2.arenhost.com

DNSSEC Not enabled

Hosting

IP Address 195.88.211.25

ASN AS214882 (ArenHost - Hadi Santosa, ID)

Provider ArenHost - Hadi Santosa, ID

Data source: rdap (1.7s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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