Infrastructure - https://timhopam.com BeaverCheck Audit

D

Multi-Resolver DNS Speed

Action

Mean 249ms across 3 resolvers (spread 419ms)

FIX

Mean 249ms across 3 resolvers (spread 419ms)

Cloudflare: 3ms

Got: 3ms via 1.1.1.1:53

Google: 324ms

Got: 324ms via 8.8.8.8:53

Quad9: 422ms

Got: 422ms via 9.9.9.9:53

High latency spread between resolvers: 419ms (min 3ms / max 422ms)

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

HTTP Probe Timing

Action

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

FIX

DNS Lookup

725 ms

TCP Connect

375 ms

TLS Handshake

378 ms

Time to First Byte

1.85 s

Total Time

2.60 s

Connection waterfall

DNS Lookup 725 ms TCP Connect 375 ms TLS Handshake 378 ms Server Processing 376 ms Content Transfer 750 ms

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, 802 ms lookup

REVIEW

1 A records, 802 ms lookup

Resolves to 1 IPv4 address(es)

Got: 45.252.249.26

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

3 nameserver(s) configured

Got: ns2.inet.vn, ns1.inet.vn, ns3.inet.vn

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution is slow (802 ms)

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

Got: 802 ms

A	45.252.249.26
AAAA	—
CNAME	—
NS	ns2.inet.vn, ns1.inet.vn, ns3.inet.vn
MX	—
TXT	google-site-verification=xpLquP4LGcH7S9DCOC_PaFCt_kv9tajp861Sne-bCmo
CAA	Lookup not available with standard resolver

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

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)

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.

C

Reverse DNS

Action

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

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

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

64 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

64

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+

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://timhopam.com

https://timhopam.com

1177 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://timhopam.com	200	1177 ms	HTTP/1.1	LiteSpeed

A+

Crawlability

robots.txt present, sitemap with 27 URLs

PASS

robots.txt present, sitemap with 27 URLs

robots.txt is present

Got: 766 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 27 entries

Sitemap index with 27 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 766 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *

# 1. Chặn các đường dẫn quản trị và hệ thống
Disallow: /wp-admin/
Disallow: /wp-login.php
Disallow: /wp-includes/
Disallow: /xmlrpc.php
Disallow: /readme.html

# 2. Mở cho phép tải tài nguyên hệ thống
Allow: /wp-admin/admin-ajax.php
Allow: /wp-content/uploads/
Allow: /wp-content/plugins/
Allow: /wp-content/themes/

# 3. Chặn các đường dẫn trùng lặp, phân trang, bộ lọc và tham số
Disallow: /*/feed
Disallow: /*/feed/
Disallow: /feed/
Disallow: /?s=
Disallow: /search/
Disallow: /category/*/page/
Disallow: /category/song/page/
Disallow: /*/page/
Disallow: /*?orderby=*
Disallow: /*?nhac-si_sort=*
Disallow: /*?ca-si_sort=*
Disallow: /*?*

# 4. Sitemaps
Sitemap: https://timhopam.com/sitemap_index.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 27 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: non-www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

301https://www.timhopam.com/

200https://timhopam.com/

Preferred variant: non-www

HTTP → HTTPS

301http://timhopam.com/ → https://timhopam.com/

Consistent

A+

Domain Intelligence

timhopam.com — via iNET SOFTWARE COMPANY LIMITED, 25 days old, hosted on AZDIGI-AS-VN - AZDIGI Corporation, VN

PASS

timhopam.com — via iNET SOFTWARE COMPANY LIMITED, 25 days old, hosted on AZDIGI-AS-VN - AZDIGI Corporation, VN

Domain registered until Sep 5, 2027 (11 months remaining)

Domain is only 25 days 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 Sep 5, 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: iNET SOFTWARE COMPANY LIMITED

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: AZDIGI-AS-VN - AZDIGI Corporation, VN

Got: AS63760

Domain expiry

336 days

September 5, 2027

SSL certificate

64 days

Issued by Let's Encrypt

Domain age

25 days

Registered September 5, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AZDIGI-AS-VN - AZDIGI Corporation, VN

ASN AS63760

45.252.249.26

Registrar

iNET SOFTWARE COMPANY LIMITED

Unlocked 3 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 iNET SOFTWARE COMPANY LIMITED

Created September 5, 2026 (25 days ago)

Expires September 5, 2027 (11 months)

Last Updated September 5, 2026

Name Servers ns1.inet.vn, ns2.inet.vn, ns3.inet.vn

DNSSEC Not enabled

Hosting

IP Address 45.252.249.26

ASN AS63760 (AZDIGI-AS-VN - AZDIGI Corporation, VN)

Provider AZDIGI-AS-VN - AZDIGI Corporation, VN

Data source: rdap (1.0s)

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