Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

200 OK

Checks

8 PASS 7 REVIEW 2 FIX

Multi-Resolver DNS Speed

Action

Mean 238ms across 3 resolvers (spread 694ms)

FIX

Mean 238ms across 3 resolvers (spread 694ms)

Quad9: 1ms

Got: 1ms via 9.9.9.9:53

Google: 19ms

Got: 19ms via 8.8.8.8:53

Cloudflare: 695ms

Got: 695ms via 1.1.1.1:53

High latency spread between resolvers: 694ms (min 1ms / max 695ms)

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.

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.

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).

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.

Reverse DNS

0/8 IPs match cert SAN

REVIEW

0/8 IPs match cert SAN

PTR for 14.238.143.151 does not match any cert SAN: static.vnpt.vn

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 14.238.143.173 does not match any cert SAN: static.vnpt.vn

PTR for 14.238.143.148 does not match any cert SAN: static.vnpt.vn

PTR for 14.238.143.154 does not match any cert SAN: static.vnpt.vn

PTR for 2001:ee0:2f06:2a::40 does not match any cert SAN: static.vnpt.vn

PTR for 2001:ee0:2f06:2a::15 does not match any cert SAN: static.vnpt.vn

PTR for 2001:ee0:2f06:2a::19 does not match any cert SAN: static.vnpt.vn

PTR for 2001:ee0:2f06:2a::16 does not match any cert SAN: static.vnpt.vn

HTTP Probe Timing

Action

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

REVIEW

DNS Lookup

337 ms

TCP Connect

295 ms

TLS Handshake

298 ms

Time to First Byte

1.32 s

Total Time

1.90 s

Connection waterfall

DNS Lookup 337 ms TCP Connect 295 ms TLS Handshake 298 ms Server Processing 388 ms Content Transfer 586 ms

TLS Certificate Expiry & Recommendations

151 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

151

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

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.

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.

DNS Records

4 A records, 339 ms lookup

PASS

4 A records, 339 ms lookup

Resolves to 4 IPv4 address(es)

Got: 14.238.143.151, 14.238.143.173, 14.238.143.148, 14.238.143.154

Has 4 IPv6 (AAAA) record(s)

Got: 2001:ee0:2f06:2a::40, 2001:ee0:2f06:2a::15, 2001:ee0:2f06:2a::19, 2001:ee0:2f06:2a::16

4 nameserver(s) configured

Got: zans2.zadns.vn, zans1.zadns.vn, zans1.zadns.me, zans2.zadns.me

No MX records — email not configured via DNS

SPF record present in TXT

DNS resolution is slow (339 ms)

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

Got: 339 ms

A	14.238.143.151, 14.238.143.173, 14.238.143.148, 14.238.143.154
AAAA	2001:ee0:2f06:2a::40, 2001:ee0:2f06:2a::15, 2001:ee0:2f06:2a::19, 2001:ee0:2f06:2a::16
CNAME	—
NS	zans2.zadns.vn, zans1.zadns.vn, zans1.zadns.me, zans2.zadns.me
MX	—
TXT	SPF v=spf1 mx -all amazonses:cuRvJrU/twGv9IMc++WZxPDD0DLAb+gsu/SEXFdS1jI= SPF v=spf1 include:amazonses.com include:_spf.google.com include:mail.zendesk.com in... facebook-domain-verification=k1qyjyd93zn4z44c2sm3dmh0slnj5e
CAA	Lookup not available with standard resolver

Resolved in 339 ms

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 redirect data available

PASS

No redirect data available

No redirect data captured

A+

IPv6 Readiness

IPv6 reachable (219 ms)

PASS

IPv6 reachable (219 ms)

IPv6 is configured and reachable at 2001:ee0:2f06:2a::40, 2001:ee0:2f06:2a::15, 2001:ee0:2f06:2a::19, 2001:ee0:2f06:2a::16

Got: 219 ms connect

IPv6 Ready

AAAA Records 2001:ee0:2f06:2a::40, 2001:ee0:2f06:2a::15, 2001:ee0:2f06:2a::19, 2001:ee0:2f06:2a::16 Connection Reachable (219 ms)

A+

Crawlability

robots.txt present, sitemap with 1359 URLs

PASS

robots.txt present, sitemap with 1359 URLs

robots.txt is present

Got: 292 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 1359 entries

Sitemap index with 1359 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 292 B Sitemaps referenced 3 User-agents * Blocking No — crawling allowed

User-agent: *
Allow: /
Disallow: /*?date=
Disallow: /tim-kiem/
Disallow: /search/
Disallow: /*?s=
Disallow: /*?q=
Disallow: /?

Sitemap: https://baomoi.com/sitemaps/sitemap.xml
Sitemap: https://baomoi.com/sitemaps/tien-ich/sitemap.xml
Sitemap: https://baomoi.com/sitemaps/bong-da/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 1359 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.baomoi.com/

200https://baomoi.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

baomoi.com — via NameCheap, Inc., 21 years, 8 months old

PASS

baomoi.com — via NameCheap, Inc., 21 years, 8 months old

Domain registered until Mar 28, 2029 (2 years, 7 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: NameCheap, 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.

Domain expiry

941 days

March 28, 2029

SSL certificate

151 days

Issued by DigiCert Inc

Domain age

21 years, 8 months

Registered March 28, 2005

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2001:ee0:2f06:2a::40

Registrar

NameCheap, 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 NameCheap, Inc.

Created March 28, 2005 (21 years, 8 months ago)

Expires March 28, 2029 (2 years, 7 months)

Last Updated January 15, 2025

Name Servers zans1.zadns.me, zans1.zadns.vn, zans2.zadns.me, zans2.zadns.vn

DNSSEC Not enabled

Hosting

IP Address 2001:ee0:2f06:2a::40

Data source: rdap (0.1s)

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+

CDN Cache Observability

Cache state: fresh (Age=0)

PASS

Cache state: fresh (Age=0)

CDN cache state observable via 1 header(s)

Got: age=0

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.