Skip to content
https://evergabe.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
65
GRADE
D
FIX
2
REVIEW
12
PASS
2
INFO
1
Probed from Singapore, Singapore
302 Found
Checks
17
2 PASS 12 REVIEW 2 FIX
F
Multi-Resolver DNS Speed
Action
All public resolvers failed to resolve the domain
FIX
All public resolvers failed to resolve the domain
Critical::
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
Warning::
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.

B
DNS Records
4 A records, 367 ms lookup
REVIEW
4 A records, 367 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 80.158.24.209, 80.158.24.211, 80.158.25.221, 80.158.25.222
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: 7ee55137aaca4157a00fff41e748b486.otcwaf.com
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'.
Warning::
DNS resolution is slow (367 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 367 ms
A80.158.24.209, 80.158.24.211, 80.158.25.221, 80.158.25.222
AAAA—
CNAME7ee55137aaca4157a00fff41e748b486.otcwaf.com
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 367 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

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

C
DNSSEC
Action
DNSSEC posture not checked
REVIEW
DNSSEC posture not checked
Info::
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
Info::
CAA records not checked
Could not query the resolver for CAA records. Network or resolver outage.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 80.158.24.209: lookup 80.158.24.209: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 80.158.24.211: lookup 80.158.24.211: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 80.158.25.221: lookup 80.158.25.221: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 80.158.25.222: lookup 80.158.25.222: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Redirect Chain
1 redirect(s), 3048 ms total
REVIEW
1 redirect(s), 3048 ms total
Info::
Single redirect
Got: https://www.evergabe.com → https://www.evergabe.com/en/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.evergabe.com
Warning::
Redirect overhead: 3048 ms total
Got: 3048 ms

https://www.evergabe.com

1397 ms · HTTP/1.1

302

https://www.evergabe.com/en/

1651 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.evergabe.com3021397 msHTTP/1.1CloudWAF
2https://www.evergabe.com/en/2001651 msHTTP/1.1CloudWAF

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

200https://www.evergabe.com/
https://evergabe.com/

HTTP → HTTPS

http://www.evergabe.com/

HTTP version does not redirect to HTTPS

C
HTTP Probe Timing
Action
Total 1583 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
563 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
242 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
487 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.58 s
Total Time Total request time from DNS lookup through full response.
1.58 s

Connection waterfall

DNS Lookup 563 ms TCP Connect 242 ms TLS Handshake 487 ms Server Processing 290 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
226 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

226
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
Info::
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
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A
Crawlability
no robots.txt, sitemap with 363 URLs
PASS
no robots.txt, sitemap with 363 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 363 entries

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

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 200 OK
Type URL Set URLs 363 entries Valid XML Yes
Sample URLs:
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.

Send Feedback