Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations261 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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
ADNS Records1 A records, 421 ms lookupPASS
| A | 54.190.248.124 |
| AAAA | — |
| CNAME | — |
| NS | vip3.alidns.com, vip4.alidns.com |
| MX | 10 mx.zoho.com 20 mx2.zoho.com 50 mx3.zoho.com |
| TXT | google-site-verification=f536dA6gSo5Yb3JD2fJbEi5_dTGB-JQB0dCli7NWML4 MS=AF456BC879837F5C53FAD218D30AB7D721BF554E google-site-verification=Eewzs3r97-f4d_wDU16c3MUmEpAG8x38JDgMxenzsjE SPF v=spf1 include:zohomail.com ~all google-site-verification=NbD_cjkf6Oy38HxwTsSdT6EFYCg13EYIaI63wEnM20I google-site-verification=on6R1gFBW8kXs8oulqW-gu82-4A1zJjAmmbnJS9xSK8 |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
ARedirect Chain1 redirect(s), 848 ms totalPASS
https://easeus.com
688 ms · HTTP/1.1
https://www.easeus.com/
160 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://easeus.com | 301 | 688 ms | HTTP/1.1 | nginx |
| 2 | https://www.easeus.com/ | 200 | 160 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 7191 URLsPASS
# Robots.txt file from https://www.easeus.com
#
# All robots will spider the domain
User-agent: *
Disallow:/easeusweb.easeus.com/
Disallow:/blog/
Disallow:/forum/
Disallow:/cgi-bin/
Disallow:/crm/
Disallow:/update/
Disallow:/ad/
Disallow:/purchase/
Disallow:/link/
Disallow:/App/
Disallow:/admin.php
Disallow:/popup/
Disallow:/reseller/
Disallow:/statictics.txt
Disallow:/statistics.php
Disallow:/language/
Disallow:/languages/
Disallow:/data-recovery-faq/
Disallow:/datarecoverywizardpro/help/
Disallow:/giveaways/
Disallow:/support-center/
Disallow:/support-center-back/
Disallow:/datarecoverywizard/faq/
Disallow:/disk-copy/help/
Disallow:/landing/
Disallow:/mail/
Disallow:/pulic/
Disallow:/article/
Disallow:/*?
Disallow:/ppc/
Disallow:/test-test111/
Disallow:/*.html.md$
Disallow:/*.md$
Disallow:/*.htm.md$
Sitemap:https://www.easeus.com/sitemap.xml
- https://www.easeus.com/questions/backup/does-intenso-ssd-have-cloning-software.html
- https://www.easeus.com/key-finder/find-twitter-password-without-resetting.html
- https://www.easeus.com/computer-instruction/working-on-updates-100-dont-turn-off.html
- https://www.easeus.com/backup-recovery/winpe-builder.html
- https://www.easeus.com/backup-recovery/windows-11-kb5044384-download.html
A+Domain Intelligenceeaseus.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 21 years, 11 months old, hosted on AWSPASS
1899 days
August 27, 2031
261 days
Issued by DigiCert Inc
21 years, 11 months
Registered August 27, 2004
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
54.190.248.124
Alibaba Cloud Computing (Beijing) Co., Ltd.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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