Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 1633 ms totalREVIEW
https://nameslink.com
971 ms · HTTP/1.1
https://www.nameslink.com/
663 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://nameslink.com | 301 | 971 ms | HTTP/1.1 | istio-envoy |
| 2 | https://www.nameslink.com/ | 200 | 663 ms | HTTP/1.1 | Tengine |
See the visual redirect chain in the HTTP Probe tab →
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations190 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 Records4 A records, 155 ms lookupPASS
| A | 47.76.239.145, 47.86.29.196, 47.86.9.184, 47.83.188.49 |
| AAAA | 240b:4001:164:6300:f77:cd1b:908d:1d0f, 240b:4001:164:6301:36f7:89ea:daa7:a569, 240b:4001:164:6301:36f7:89ea:daa7:a566, 240b:4001:164:6300:f77:cd1b:908d:1d12 |
| CNAME | gw-3f69e8ae35ee441493650e7cce223cf7.cn-hongkong.alicloudapi.com |
| NS | vip3.alidns.com, vip4.alidns.com |
| MX | 5 mx1.qiye.aliyun.com 10 mx2.qiye.aliyun.com 15 mx3.qiye.aliyun.com |
| TXT | SPF v=spf1 include:spf.qiye.aliyun.com -all _globalsign-domain-verification=wHVfG2TH3aUaLfH-V3hPfwSWil7OnWpsAdn4o5wjkw |
| CAA | Lookup not available with standard resolver |
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
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
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.
A+Crawlabilityrobots.txt present, sitemap with 2 URLsPASS
User-agent: *
Allow: *
Sitemap: https://www.nameslink.com/sitemap.xml
A+Domain Intelligencenameslink.com — via Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn), 26 years, 11 months old, hosted on Alibaba CloudPASS
113 days
October 6, 2026
190 days
Issued by DigiCert Inc
26 years, 11 months
Registered October 6, 1999
Not enabled
Protects against DNS spoofing
Alibaba Cloud
ASN AS45102
47.86.9.184
Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)
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