Skip to content
https://mizan-money-venhw2.v2.appdeploy.ai/⁠

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
6
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 6 REVIEW 1 FIX
D
Crawlability
Action
robots.txt present, no sitemap
FIX
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 68 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 68 B Sitemaps referenced 0 User-agents facebookexternalhit, * Blocking Yes — all crawlers blocked
User-agent: facebookexternalhit
Allow: /

User-agent: *
Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
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)
Info::
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/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 18.154.43.114 does not match any cert SAN: server-18-154-43-114.mad53.r.cloudfront.net
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.
Info::
PTR for 18.154.43.67 does not match any cert SAN: server-18-154-43-67.mad53.r.cloudfront.net
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.
Info::
PTR for 18.154.43.96 does not match any cert SAN: server-18-154-43-96.mad53.r.cloudfront.net
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.
Info::
PTR for 18.154.43.117 does not match any cert SAN: server-18-154-43-117.mad53.r.cloudfront.net
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
Info::
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
175 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

175
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
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
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.
A
DNS Records
4 A records, 39 ms lookup
PASS
4 A records, 39 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 18.154.43.114, 18.154.43.67, 18.154.43.96, 18.154.43.117
Info::
No IPv6 (AAAA) records
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 39 ms
Got: 39 ms
A18.154.43.114, 18.154.43.67, 18.154.43.96, 18.154.43.117
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 39 ms

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)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 24ms across 3 resolvers (spread 11ms)
PASS
Mean 24ms across 3 resolvers (spread 11ms)
Info::
Quad9: 18ms
Got: 18ms via 9.9.9.9:53
Info::
Cloudflare: 25ms
Got: 25ms via 1.1.1.1:53
Info::
Google: 29ms
Got: 29ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://mizan-money-venhw2.v2.appdeploy.ai/⁠

https://mizan-money-venhw2.v2.appdeploy....

326 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mizan-money-venhw2.v2.appdeploy....200326 msHTTP/1.1AmazonS3
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.mizan-money-venhw2.v2.appdeploy.ai/⁠
200https://mizan-money-venhw2.v2.appdeploy.ai/⁠

Trailing Slash

404https://mizan-money-venhw2.v2.appdeploy.ai/⁠/
200https://mizan-money-venhw2.v2.appdeploy.ai/⁠

HTTP → HTTPS

301http://mizan-money-venhw2.v2.appdeploy.ai/⁠ → https://mizan-money-venhw2.v2.appdeploy.ai/%E2%81%A0

Consistent

A+
Domain Intelligence
appdeploy.ai — via Tucows Domains Inc., 10 months old
PASS
appdeploy.ai — via Tucows Domains Inc., 10 months old
Info::
Domain registered until Dec 24, 2027 (1 years, 1 months remaining)
Info::
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.
Info::
Registrar: Tucows Domains Inc.
Warning::
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

396 days

December 24, 2027

SSL certificate

175 days

Issued by Amazon

Domain age

10 months

Registered December 24, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:2091:e600:12:e062:d680:93a1

Registrar

Tucows Domains 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 Tucows Domains Inc.
Created December 24, 2025 (10 months ago)
Expires December 24, 2027 (1 years, 1 months)
Last Updated August 12, 2026
Name Servers ns-1381.awsdns-44.org, ns-1855.awsdns-39.co.uk, ns-236.awsdns-29.com, ns-791.awsdns-34.net
DNSSEC Not enabled
Registrant FREEBRAAVOS LTD
Hosting
IP Address 2600:9000:2091:e600:12:e062:d680:93a1
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 536 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
34 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
356 ms
Total Time Total request time from DNS lookup through full response.
536 ms

Connection waterfall

DNS Lookup 34 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 314 ms Content Transfer 180 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Document is served via AWS CloudFront CDN (edge: MAD53-P2)
Got: x-amz-cf-id: -E9a6yCKclaRra53ILLyqVCBf862aWBYVZ9cP1B66oR3iCh8nQlKWw==
Info::
CDN cache status: Miss from cloudfront
Document served via CDN: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: -E9a6yCKclaRra53ILLyqVCBf862aWBYVZ9cP1B66oR3iCh8nQlKWw==
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=Miss from cloudfront
A+
Health Check Endpoint
Health endpoint at https://mizan-money-venhw2.v2.appdeploy.ai/health (HTTP 200)
PASS
Health endpoint at https://mizan-money-venhw2.v2.appdeploy.ai/health (HTTP 200)
Info::
Public health endpoint at https://mizan-money-venhw2.v2.appdeploy.ai/health
Got: https://mizan-money-venhw2.v2.appdeploy.ai/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback