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 & Recommendations181 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
A+DNS Records1 A records, 40 ms lookupPASS
| A | 190.92.221.14 |
| AAAA | — |
| CNAME | — |
| NS | ns-525.awsdns-01.net, ns-64.awsdns-08.com, ns-1058.awsdns-04.org, ns-1600.awsdns-08.co.uk |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | google-site-verification=Huc-ZY40j6fkIoDtqE6jAbMs2OsQk8iZGEfBGxM8j-o SPF v=spf1 include:amazonses.com include:_SPF.Google.com ~all google-site-verification=bBgwHYxQX1tly9tf8RwtriWtkhTl9T73XVQ9AMBCafQ 2017082800000020y7yxe150ek5y8555hk5bbxlclnje6uf7ez5rm87rjdpvyrg7 google-site-verification=GJmCX_5kV344x7lo2KRUOVcKAvLa2QiyzfCb8-SQu6Q google-site-verification=2LuGUyVmlVxB4KESPxbVuZkqQKx0NC4Zob7TLWRKWag google-site-verification=L05ZRouFNapVhDuQnxvJGiBIrfrpQDiHPC_3DyH7ROk ab655b73d42a468299b95b89cc03a449 google-site-verification=y82L47wGlBdkCPwSzHzdi24ZGZNgN2m00MW1zH3MDJY google-site-verification=zqxia10BaeOPQe0m-YgFOpQfgc6beWqYJXDRSTQiqE0 phb7h3rylq6xg4z8hvhxh6h10b7t4pkw yandex-verification: 9f65f913a932dd9c google-site-verification=0bvJqACoxoHiEZCUV_BRjq6HPiJUP34Xr_HrSkF6GIQ google-site-verification=WZkgTqms06Y_ddJdRC-4JF_a2TghOHyV0aUQfN7nQ0c google-site-verification=hKBQypFimzlyfEft0EPRkDqGZrDFzS9gqKtVXaF3_G4 |
| 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.
ARedirect Chain1 redirect(s), 826 ms totalPASS
https://wps.com
724 ms · HTTP/1.1
https://www.wps.com/
101 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://wps.com | 301 | 724 ms | HTTP/1.1 | elb |
| 2 | https://www.wps.com/ | 200 | 101 ms | HTTP/1.1 | elb |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 4 URLsPASS
User-agent: *
Disallow: /hp-upgrade
Disallow: /newsite
Disallow: /newwps
Disallow: /d/
Sitemap: https://www.wps.com/sitemap.xml
A+Domain Intelligencewps.com — via Dominet (HK) Limited, 33 years, 8 months old, hosted on HWCLOUDS-AS-AP HUAWEI CLOUDS, HKPASS
3483 days
January 26, 2036
181 days
Issued by DigiCert, Inc.
33 years, 8 months
Registered January 25, 1993
Not enabled
Protects against DNS spoofing
HWCLOUDS-AS-AP HUAWEI CLOUDS, HK
ASN AS136907
190.92.221.14
Dominet (HK) Limited
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