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 Santa Clara, United States

200 OK

Checks

3 PASS 12 REVIEW 1 FIX

Multi-Resolver DNS Speed

Action

All public resolvers failed to resolve the domain

FIX

All public resolvers failed to resolve the domain

DNS resolution failed against all public resolvers

1.1.1.1, 8.8.8.8, and 9.9.9.9 all failed to resolve this domain. Almost always means the domain is delegated incorrectly, the authoritative servers are unreachable, or the resolution returned NXDOMAIN/SERVFAIL across the board.

DNSSEC

Action

DNSSEC posture not checked

REVIEW

DNSSEC posture not checked

Could not query the validating resolver for DNSSEC status. Network or resolver outage.

CAA Records

Action

CAA posture not checked

REVIEW

CAA posture not checked

CAA records not checked

Could not query the resolver for CAA records. Network or resolver outage.

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 185.165.185.86 does not match any cert SAN: neastin.com

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.

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

HTTP version does not redirect to HTTPS

Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

https://www.evaprints.ro/

200https://evaprints.ro/

HTTP → HTTPS

http://evaprints.ro/

HTTP version does not redirect to HTTPS

HTTP Probe Timing

Action

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

REVIEW

DNS Lookup

372 ms

TCP Connect

183 ms

TLS Handshake

193 ms

Time to First Byte

988 ms

Total Time

1.54 s

Connection waterfall

DNS Lookup 372 ms TCP Connect 183 ms TLS Handshake 193 ms Server Processing 241 ms Content Transfer 548 ms

TLS Certificate Expiry & Recommendations

60 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 & Delivery

Action

Assets on Akamai (host analytics.tiktok.com, 3 assets); document served directly from origin

REVIEW

Assets on Akamai (host analytics.tiktok.com, 3 assets); document served directly from origin

Document not behind existing CDN (Akamai serves the assets)

The page's subresources are delivered by Akamai (analytics.tiktok.com, 3 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.

Got: delegation e35058.api11.akamaiedge.net

Assets on Akamai: analytics.tiktok.com (assets: 3), cache TCP_MEM_HIT from a23-216-148-205.deploy.akamaitechnologies.com (AkamaiGHost/22.6.3-da071da6976b6d633b0b37bcfe65c0fc) (-)

Got: delegation e35058.api11.akamaiedge.net

Assets on a CDN, document is not: Akamai

Document origin not attributed

Asset hosts on a CDN

analytics.tiktok.com — Akamai · assets: 3 · Cache Status: TCP_MEM_HIT from a23-216-148-205.deploy.akamaitechnologies.com (AkamaiGHost/22.6.3-da071da6976b6d633b0b37bcfe65c0fc) (-)

Other asset hosts

connect.facebook.net — assets: 2 · below probe threshold
unpkg.com — assets: 2 · below probe threshold
cdnjs.cloudflare.com — assets: 1 · below probe threshold
googleads.g.doubleclick.net — assets: 1 · below probe threshold
www.googletagmanager.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

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

DNS Records

1 A records, 409 ms lookup

PASS

1 A records, 409 ms lookup

Resolves to 1 IPv4 address(es)

Got: 185.165.185.86

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.gazduire.net, ns2.gazduire.net

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (409 ms)

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

Got: 409 ms

A	185.165.185.86
AAAA	—
CNAME	—
NS	ns1.gazduire.net, ns2.gazduire.net
MX	10 mail.evaprints.ro
TXT	google-site-verification=5F2ED_Tf79QpR4aD-544HSj9Au4Fl0I3BWb7aPV0QrM SPF v=spf1 a mx ip4:185.165.185.2 ~all
CAA	Lookup not available with standard resolver

Resolved in 409 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://evaprints.ro

https://evaprints.ro

972 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://evaprints.ro	200	972 ms	HTTP/1.1

Domain Intelligence

Domain intelligence data not available

INFO

Domain intelligence data not available

RDAP and WHOIS lookup both failed

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