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

6 PASS 9 REVIEW 2 FIX

HTTP Probe Timing

Action

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

FIX

DNS Lookup

55 ms

TCP Connect

105 ms

TLS Handshake

588 ms

Time to First Byte

9.57 s

Total Time

9.57 s

Connection waterfall

DNS Lookup 55 ms TCP Connect 105 ms TLS Handshake 588 ms Server Processing 8.82 s Content Transfer 1 ms

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.

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

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 66.102.137.24 does not match any cert SAN: sh-cp38.yyz2.servername.online

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.

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

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.

Domain Intelligence

valatir.com — via Promo People, Inc., 1 years old, hosted on ONIAAS - HostPapa, US

REVIEW

valatir.com — via Promo People, Inc., 1 years old, hosted on ONIAAS - HostPapa, US

Domain expires in 1 days

This domain expires on November 15, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Got: Expires Nov 15, 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: Promo People, 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.

Hosting: ONIAAS - HostPapa, US

Got: AS40092

Domain expiry

Expires today

November 15, 2026

SSL certificate

39 days

Issued by Let's Encrypt

Domain age

1 years

Registered November 15, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

ONIAAS - HostPapa, US

ASN AS40092

66.102.137.24

Registrar

Promo People, Inc.

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 Promo People, Inc.

Created November 15, 2025 (1 years ago)

Expires November 15, 2026 (1 days)

Last Updated November 15, 2025

Name Servers ns1.hostpapa.com, ns2.hostpapa.com

DNSSEC Not enabled

Hosting

IP Address 66.102.137.24

ASN AS40092 (ONIAAS - HostPapa, US)

Provider ONIAAS - HostPapa, US

Data source: rdap (0.3s)

This domain expires on November 15, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

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

TLS Certificate Expiry & Recommendations

39 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

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

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.

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.

A+

DNS Records

1 A records, 54 ms lookup

PASS

1 A records, 54 ms lookup

Resolves to 1 IPv4 address(es)

Got: 66.102.137.24

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: ns1.hostpapa.com, ns2.hostpapa.com

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 54 ms

Got: 54 ms

A	66.102.137.24
AAAA	—
CNAME	—
NS	ns1.hostpapa.com, ns2.hostpapa.com
MX	0 valatir.com
TXT	SPF v=spf1 +a +mx +ip4:66.102.137.24 +include:spf.servername.online ~all
CAA	Lookup not available with standard resolver

Resolved in 54 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+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

CAA Records

issue: sectigo.com, pki.goog, globalsign.com, letsencrypt.org | issuewild: sectigo.com, pki.goog, letsencrypt.org, globalsign.com

PASS

issue: sectigo.com, pki.goog, globalsign.com, letsencrypt.org | issuewild: sectigo.com, pki.goog, letsencrypt.org, globalsign.com

CAA issue tag present — authorized CA(s): sectigo.com, pki.goog, globalsign.com, letsencrypt.org

No CAA iodef tag — won't be notified of failed issuance attempts

Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.

Multi-Resolver DNS Speed

Mean 59ms across 3 resolvers (spread 12ms)

PASS

Mean 59ms across 3 resolvers (spread 12ms)

Google: 53ms

Got: 53ms via 8.8.8.8:53

Cloudflare: 61ms

Got: 61ms via 1.1.1.1:53

Quad9: 65ms

Got: 65ms via 9.9.9.9:53

A+

Redirect Chain

No redirect data available

PASS

No redirect data available

No redirect data captured

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.valatir.com/

200https://valatir.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

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