Skip to content
https://geteasy.ai

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
302 Found
Checks
17
9 PASS 8 REVIEW
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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 104.21.9.239: lookup 104.21.9.239: no such host
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 172.67.131.19: lookup 172.67.131.19: no such host
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 2606:4700:3033::6815:9ef: lookup 2606:4700:3033::6815:9ef: no such host
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 2606:4700:3030::ac43:8313: lookup 2606:4700:3030::ac43:8313: no such host
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), 1032 ms total
REVIEW
1 redirect(s), 1032 ms total
Info::
Single redirect
Got: https://geteasy.ai → https://geteasy.ai/en (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://geteasy.ai
Warning::
Redirect overhead: 1032 ms total
Got: 1032 ms

https://geteasy.ai

506 ms · HTTP/1.1

302

https://geteasy.ai/en

526 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://geteasy.ai302506 msHTTP/1.1cloudflare
2https://geteasy.ai/en200526 msHTTP/1.1cloudflare

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

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 302 Expected: 301 redirect to HTTPS

www / non-www

https://www.geteasy.ai/
200https://geteasy.ai/

HTTP → HTTPS

302http://geteasy.ai/ → /en

HTTP version does not redirect to HTTPS

B
TLS Certificate Expiry & Recommendations
64 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

64
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
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: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 35 ms lookup
PASS
2 A records, 35 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.9.239, 172.67.131.19
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3033::6815:9ef, 2606:4700:3030::ac43:8313
Info::
2 nameserver(s) configured
Got: hal.ns.cloudflare.com, tina.ns.cloudflare.com
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 35 ms
Got: 35 ms
A104.21.9.239, 172.67.131.19
AAAA2606:4700:3033::6815:9ef, 2606:4700:3030::ac43:8313
CNAME—
NShal.ns.cloudflare.com, tina.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
SPF v=spf1 +include:spf.onlarksuite.com include:_spf.google.com ~all
google-site-verification=AlefysU74wrkoPOY0A9mYuxWFUffKZDgpI3doou7GKw
ahrefs-site-verification_b9a9525f9290f4ee3a9a1787d304aec9acaf70679462016c581e9e3...
zalo-platform-site-verification=FDk61Cxa00T8-gKacSbsVqd3tLMbjGm3CpKu
verification-code-site-App_lark=1BiSDjtuVFKXaWj5uodD
CAALookup not available with standard resolver
Resolved in 35 ms
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 18ms across 3 resolvers (spread 21ms)
PASS
Mean 18ms across 3 resolvers (spread 21ms)
Info::
Quad9: 6ms
Got: 6ms via 9.9.9.9:53
Info::
Cloudflare: 23ms
Got: 23ms via 1.1.1.1:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3033::6815:9ef, 2606:4700:3030::ac43:8313
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3033::6815:9ef, 2606:4700:3030::ac43:8313 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 902 URLs
PASS
robots.txt present, sitemap with 902 URLs
Info::
robots.txt is present
Got: 63 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 902 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 63 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://geteasy.ai/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 902 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
geteasy.ai — via NameCheap, Inc., 1 years, 8 months old
PASS
geteasy.ai — via NameCheap, Inc., 1 years, 8 months old
Info::
Domain registered until Jan 7, 2027 (3 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: NameCheap, 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

107 days

January 7, 2027

SSL certificate

64 days

Issued by Google Trust Services

Domain age

1 years, 8 months

Registered January 7, 2025

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3030::ac43:8313

Registrar

NameCheap, Inc.

Unlocked 2 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 NameCheap, Inc.
Created January 7, 2025 (1 years, 8 months ago)
Expires January 7, 2027 (3 months)
Last Updated August 12, 2026
Name Servers tina.ns.cloudflare.com, hal.ns.cloudflare.com
DNSSEC Not enabled
Registrant Redacted for Privacy Purposes
Hosting
IP Address 2606:4700:3030::ac43:8313
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 522 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
45 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
522 ms
Total Time Total request time from DNS lookup through full response.
522 ms

Connection waterfall

DNS Lookup 45 ms TCP Connect 17 ms TLS Handshake 22 ms Server Processing 439 ms Content Transfer 0 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a3b52d394951d0bf-CDG
Info::
CDN cache status: DYNAMIC
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a3b52d394951d0bf-CDG
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback