Skip to content
https://digikey.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
3 PASS 5 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, sitemap with 5259 URLs
REVIEW
robots.txt present, sitemap with 5259 URLs
Info::
robots.txt is present
Got: 896 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Info::
sitemap.xml contains 5259 entries
Info::
Sitemap index with 5259 child sitemaps
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

robots.txt 200 OK
Size 896 B Sitemaps referenced 3 User-agents MJ12bot, PetalBot, Yandex, *, AdsBot-Google, AdIdxBot, AhrefsBot, dotbot Blocking No — crawling allowed
# all crawlers

User-agent: *


Disallow: /MyDigiKey/*

Disallow: /MyDigiKey

Disallow: /mobile/api/*

Disallow: /VoiceAssistant/*

Disallow: /system/templates/*

Disallow: /system/cb/*

Disallow: /OrderHistory


# Google-Adsbot

User-agent: AdsBot-Google


Disallow: /MyDigiKey/*

Disallow: /MyDigiKey

Disallow: /api/subsTable/


# Bing-Adsbot

User-agent: AdIdxBot


Disallow: /MyDigiKey/*

Disallow: /MyDigiKey

Disallow: /api/subsTable/


# Ahrefs

User-agent: AhrefsBot

Disallow: /


# Moz

User-agent: dotbot

Disallow: /


# Majestic

User-agent: MJ12bot

Disallow: /


# PetalBot

User-agent: PetalBot

Disallow: /


# Yandex

User-agent: Yandex

Disallow: /


# Sitemaps

Sitemap: https://www.digikey.com/product-detail/sitemap.xml

Sitemap: https://www.digikey.com/product-search/sitemap.xml

Sitemap: https://www.digikey.com/sitemap/homepage-sitemap_sitemapindex_com.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 5259 entries Valid XML No
Child Sitemaps:
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.digikey.com/
200https://digikey.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
HTTP Probe Timing
Total 914 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
227 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
456 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
914 ms
Total Time Total request time from DNS lookup through full response.
914 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 227 ms TLS Handshake 456 ms Server Processing 226 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
255 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

255
days left
0d 30d 60d 90d+

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 Records
1 A records, 28 ms lookup
PASS
1 A records, 28 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 204.221.76.76
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns1.p10.dynect.net, cmtu.mt.ns.els-gms.att.net, cbru.br.ns.els-gms.att.net, ns4.p10.dynect.net, ns3.p10.dynect.net, ns2.p10.dynect.net
Info::
3 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: 28 ms
Got: 28 ms
A204.221.76.76
AAAA—
CNAME—
NSns1.p10.dynect.net, cmtu.mt.ns.els-gms.att.net, cbru.br.ns.els-gms.att.net, ns4.p10.dynect.net, ns3.p10.dynect.net, ns2.p10.dynect.net
MX
5 mail3.digikey.com
5 mail2.digikey.com
5 mail1.digikey.com
TXT
mongodb-site-verification=eHJeJp0x4fUwUj0JFhIrXqbcESiNTYKQ
adobe-idp-site-verification=7f6e64b43ab5633a65982ba24cd393b1cb41e24f1713cb253eb1...
onetrust-domain-verification=ab8d874f515c43afb70cc2e4d3b68992
SPF v=spf1 mx a:mail1.digikey.com a:mail2.digikey.com a:mail3.digikey.com include:sp...
identrust_validate=2L2sz1c7af24CkiGGwOkTTHt2+loPoRrv6LXK2SHLsCJ
google-site-verification=tOC8mvuTbCAmX5BZdAEEBAIDRD8mI-UFpoDktgFHKx8
canva-site-verification=GHSUM9JppIqpfV62qsvNHg
onetrust-domain-verification=44e0ee11696c47749dc8b60d04593e86
docusign=84502f13-5147-4d7a-bf08-af243deea0e0
jamf-site-verification=8hIe1vXeo-UsDTw0y048Pg
apple-domain-verification=s6aLYnSxh8iDqwmJ
configcat-domain-verification=08dc62ea-d86c-4f76-832c-7b24768fd4ed
v3765SR38OkHVKeCrJOnQ+wAf9rQweLyl90gCt8EWcMh4TLwkK6QHlUidS4M4lUWeWjAom8U95OOc8CP...
Foxit-domain-verification=d1db5f796ff40925f5aa8f62196b3ed7
atlassian-domain-verification=dh9T/MmOhSZtNPGNn7kJvk7u/c/FxGHrxHiKuR/v6vFCCJQ4Lv...
CAALookup not available with standard resolver
Resolved in 28 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

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

A
Redirect Chain
1 redirect(s), 973 ms total
PASS
1 redirect(s), 973 ms total
Info::
Single redirect
Got: https://digikey.com → https://www.digikey.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 973 ms total
Got: 973 ms

https://digikey.com

919 ms · HTTP/1.0

301

https://www.digikey.com/

54 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://digikey.com301919 msHTTP/1.0
2https://www.digikey.com/20054 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
digikey.com — via CSC Corporate Domains, Inc., 31 years, 5 months old, hosted on DIGIKEY - Digi-Key Corporation, US
PASS
digikey.com — via CSC Corporate Domains, Inc., 31 years, 5 months old, hosted on DIGIKEY - Digi-Key Corporation, US
Info::
Domain registered until Apr 19, 2027 (1 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: CSC Corporate Domains, 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.
Info::
Hosting: DIGIKEY - Digi-Key Corporation, US
Got: AS14738
Domain expiry

275 days

April 19, 2027

SSL certificate

255 days

Issued by Sectigo Limited

Domain age

31 years, 5 months

Registered April 18, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

DIGIKEY - Digi-Key Corporation, US

ASN AS14738

204.221.76.76

Registrar

CSC Corporate Domains, Inc.

Unlocked 6 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 CSC Corporate Domains, Inc.
Created April 18, 1995 (31 years, 5 months ago)
Expires April 19, 2027 (1 years)
Last Updated April 15, 2026
Name Servers cbru.br.ns.els-gms.att.net, cmtu.mt.ns.els-gms.att.net, ns1.p10.dynect.net, ns2.p10.dynect.net, ns3.p10.dynect.net, ns4.p10.dynect.net
DNSSEC Not enabled
Hosting
IP Address 204.221.76.76
ASN AS14738 (DIGIKEY - Digi-Key Corporation, US)
Provider DIGIKEY - Digi-Key Corporation, US
Data source: rdap (1.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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback