Infrastructure - https://ify.ro BeaverCheck Audit

F

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.

D

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 (document or assets)

Consider using a CDN to improve global delivery speed and reduce origin load.

C

DNSSEC

Action

DNSSEC posture not checked

REVIEW

DNSSEC posture not checked

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

C

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.

B

Reverse DNS

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 37.143.166.254 does not match any cert SAN: iabi.lol

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

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

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.ify.ro/

200https://ify.ro/

HTTP → HTTPS

http://ify.ro/

HTTP version does not redirect to HTTPS

B

HTTP Probe Timing

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

REVIEW

DNS Lookup

552 ms

TCP Connect

184 ms

TLS Handshake

190 ms

Time to First Byte

1.11 s

Total Time

1.48 s

Connection waterfall

DNS Lookup 552 ms TCP Connect 184 ms TLS Handshake 190 ms Server Processing 185 ms Content Transfer 368 ms

B

TLS Certificate Expiry & Recommendations

83 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

83

days left

0d 30d 60d 90d+

Recommended actions

Add includeSubDomains to the HSTS directive
Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
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

DNS Records

1 A records, 1119 ms lookup

PASS

1 A records, 1119 ms lookup

Resolves to 1 IPv4 address(es)

Got: 37.143.166.254

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns2.ducadu.org, ns4.ducadu.org, ns1.ducadu.org, ns3.ducadu.org

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution is slow (1119 ms)

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

Got: 1119 ms

A	37.143.166.254
AAAA	—
CNAME	—
NS	ns2.ducadu.org, ns4.ducadu.org, ns1.ducadu.org, ns3.ducadu.org
MX	0 ify.ro
TXT	SPF v=spf1 ip4:37.143.170.61 ip4:37.143.166.254 include:_netblock.opticnet.ro +a +mx...
CAA	Lookup not available with standard resolver

Resolved in 1119 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://ify.ro

https://ify.ro

847 ms · HTTP/1.1 FINAL

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

A

Crawlability

robots.txt present, no sitemap

PASS

robots.txt present, no sitemap

robots.txt is present

Got: 435 bytes

No sitemap.xml found

A sitemap helps search engines discover and index your pages more efficiently.

robots.txt references sitemap

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 200 OK

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

User-agent: *
Disallow: /wp-content/uploads/wc-logs/
Disallow: /wp-content/uploads/woocommerce_transient_files/
Disallow: /wp-content/uploads/woocommerce_uploads/
Disallow: /*?add-to-cart=
Disallow: /*?*add-to-cart=
Disallow: /ify-admin/
Allow: /ify-admin/admin-ajax.php

# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: http://ify.ro/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

Domain Intelligence

Domain intelligence data not available

INFO

Domain intelligence data not available

RDAP and WHOIS lookup both failed