Skip to content
https://dlink.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
D
Redirect Chain
Action
2 redirect(s), 1724 ms total
FIX
2 redirect(s), 1724 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.dlink.com/
Warning::
Redirect overhead: 1724 ms total
Got: 1724 ms

https://dlink.com

58 ms · HTTP/1.1

301

https://www.dlink.com/

553 ms · HTTP/1.1

302

https://www.dlink.com/es/es

1112 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dlink.com30158 msHTTP/1.1cloudflare
2https://www.dlink.com/302553 msHTTP/1.1cloudflare
3https://www.dlink.com/es/es2001112 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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
TLS Certificate Expiry & Recommendations
47 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

47
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
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f08732ee80dc395-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f08732ee80dc395-CDG
A+
DNS Records
2 A records, 39 ms lookup
PASS
2 A records, 39 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.135.29, 172.66.137.42
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::ac42:871d, 2606:4700:10::ac42:892a
Info::
2 nameserver(s) configured
Got: aragorn.ns.cloudflare.com, tricia.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 39 ms
Got: 39 ms
A172.66.135.29, 172.66.137.42
AAAA2606:4700:10::ac42:871d, 2606:4700:10::ac42:892a
CNAME—
NSaragorn.ns.cloudflare.com, tricia.ns.cloudflare.com
MX
0 dlink-com.mail.protection.outlook.com
TXT
facebook-domain-verification=sjejrzw0e190l71fua4ito17uh4wtt
_mzvb4t86zse4ftesx2vokf1nvr6yucm
meeu49qil67tfucktao988ntpj
_vv36mxspoog5xh9uphvynjzg5bk8bzi
google-site-verification=_zQ9w8KpBK0LHENfKcN67_tm0wl6AJl0UF7MujaJRSU
jj44vcpv5k7q1eorkpf52v33if
SPF v=spf1 include:spf.protection.outlook.com include:vtigermails.com include:amazon...
apple-domain-verification=SKx5IozBnirmfV77
MS=D692370E9F220608D9B3146C7F5C1CA0C8A637BA
MS=ms15020137
globalsign-domain-verification=pR0zQw78fXOqwg2LmTjS1PO5gcAAki7yVrghJlr8ZX
kf5mp76qr18kl5jfwxvy6j2p1f5lq0h0
MS=A45E239A974128C2EB713001DF5FF41EF791EB90
ktcenogp2jq9mjue4h2jhih7ce
CAALookup not available with standard resolver
Resolved in 39 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::ac42:871d, 2606:4700:10::ac42:892a
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::ac42:871d, 2606:4700:10::ac42:892a Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 33 URLs
PASS
robots.txt present, sitemap with 33 URLs
Info::
robots.txt is present
Got: 262 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 33 entries
Info::
Sitemap index with 33 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 262 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Sitemap: https://www.dlink.com/sitemap-index.aspx

Allow: *?page=

Allow: *?h=

Allow: *?go=

Allow: *?v=

Allow: *?w=

Allow: *?la=

Allow: *?mode=xmlsitemap

Allow: */_include/

Allow: /*?w=

Allow: /*?gridMode

Allow: /*?revision

Disallow: /*?
sitemap.xml 200 OK
Type Sitemap Index URLs 33 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.dlink.com/
200https://dlink.com/

Preferred variant: non-www

HTTP → HTTPS

301http://dlink.com/ → https://www.dlink.com/

Consistent

A+
Domain Intelligence
dlink.com — via GoDaddy.com, LLC, 31 years, 6 months old
PASS
dlink.com — via GoDaddy.com, LLC, 31 years, 6 months old
Info::
Domain registered until Apr 6, 2031 (5 years 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: GoDaddy.com, LLC
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

1757 days

April 6, 2031

SSL certificate

47 days

Issued by Google Trust Services

Domain age

31 years, 6 months

Registered April 5, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::ac42:892a

Registrar

GoDaddy.com, LLC

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 GoDaddy.com, LLC
Created April 5, 1995 (31 years, 6 months ago)
Expires April 6, 2031 (5 years)
Last Updated April 6, 2026
Name Servers aragorn.ns.cloudflare.com, tricia.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:10::ac42:892a
Data source: rdap (0.1s)

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 95 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
40 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.
20 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
96 ms
Total Time Total request time from DNS lookup through full response.
96 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 17 ms TLS Handshake 20 ms Server Processing 19 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback