Skip to content
https://engadget.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1188 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1188 B Sitemaps referenced 0 User-agents Neevabot, Seekr, TurnitinBot, ZumBot, AwarioRssBot, Claude-Web, huggingface, img2dataset, Nutch, PiplBot, BLEXBot, ClaudeBot, FacebookBot, GPTBot, Meltwater, ChatGPT-User, cohere-ai, http://panscient.com, PerplexityBot, SeznamBot, AlphaBot, AwarioSmartBot, CCBot, Diffbot, omgili, YouBot, Bytespider, claritybot, Google-Extended, news-please, omgilibot, Perplexity-ai, Scrapy, ADmantX, ImagesiftBot, magpie-crawler, NewsNow, PetalBot, SentiBot, *, anthropic-ai, Buzzbot, FriendlyCrawler, http://scoop.it Blocking No — crawling allowed
User-agent: *
Disallow: /forward
Disallow: /traffic
Disallow: /mm_track
Disallow: /tag/expire-images*
Disallow: /_remote
Disallow: /_td_api
Disallow: /_td
Disallow: /_uac/adpage.html
Disallow: /caas/

User-Agent: ADmantX
User-Agent: AlphaBot
User-Agent: anthropic-ai
User-Agent: AwarioRssBot
User-Agent: AwarioSmartBot
User-Agent: BLEXBot
User-Agent: Buzzbot
User-Agent: Bytespider
User-Agent: CCBot
User-Agent: ChatGPT-User
User-Agent: claritybot
User-Agent: Claude-Web
User-Agent: ClaudeBot
User-Agent: cohere-ai
User-Agent: Diffbot
User-Agent: FacebookBot
User-Agent: FriendlyCrawler
User-Agent: Google-Extended
User-Agent: GPTBot
User-Agent: huggingface
User-Agent: ImagesiftBot
User-Agent: img2dataset
User-Agent: magpie-crawler
User-Agent: Meltwater
User-Agent: Neevabot
User-Agent: news-please
User-Agent: NewsNow
User-Agent: Nutch
User-Agent: omgili
User-Agent: omgilibot
User-Agent: http://panscient.com
User-Agent: Perplexity-ai
User-Agent: PerplexityBot
User-Agent: PetalBot
User-Agent: PiplBot
User-Agent: http://scoop.it
User-Agent: Scrapy
User-Agent: Seekr
User-Agent: SentiBot
User-Agent: SeznamBot
User-Agent: TurnitinBot
User-Agent: YouBot
User-Agent: ZumBot
Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.engadget.com/
200https://engadget.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://engadget.com/ https://www.engadget.com/

Consistent

B
TLS Certificate Expiry & Recommendations
154 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
2 A records, 45 ms lookup
PASS
2 A records, 45 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 13.248.158.7, 76.223.84.192
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns2.yahoo.com, ns5.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns1.yahoo.com
Info::
2 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: 45 ms
Got: 45 ms
A13.248.158.7, 76.223.84.192
AAAA
CNAME
NSns2.yahoo.com, ns5.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns1.yahoo.com
MX
10 mxb-00505701.gslb.pphosted.com
10 mxa-00505701.gslb.pphosted.com
TXT
google-site-verification=HvBevOp-2NRmXFBrAdaW5D2T4tXBwKaySkp9fKZhM1w
google-site-verification=WHAdu9KkehGzlorxbvJ2y_5amqxc3cg7tkZPOq5kfHE
dropbox-domain-verification=rsbofmkouaiq
google-site-verification=BpynUGtADw1TWA_U9Z4Zsc0u-VDU_UmwNEQMfYvYkIU
docusign=b3e8a126-9373-4583-bd30-e83928fd759d
google-site-verification=p-jBTlGibBWlkOY8GeN87lqjiXGbqOm0WT6tD9pgYOQ
google-site-verification=W43WL570BKUMJD6NVSNFZUzgKTA5BRLiZ8xJo0a-85c
bc1e9de5-142f-480d-a6b0-3c299c94521d
atlassian-domain-verification=Aqj2sFhPdaXKuzHfHJVnoasFSVYVdbez8ftp2whI0J1jaUmUtr...
MS=ms80384357
google-site-verification=R40VNFYnZpHC6Mq0oOc-eUAScx1c3_xnGaNrDFhSVc4
google-site-verification=dq63SFV-jZCnCkjtUbADJ1HHIlRV32QFjZo-bzRHI0w
SPF v=spf1 a mx include:_spf.google.com ptr:aol.com include:aspmx.sailthru.com incl...
knowbe4-site-verification=bc3830115833f4f956e30f506f1da8c8
CAALookup not available with standard resolver
Resolved in 45 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
Redirect Chain
1 redirect(s), 742 ms total
PASS
1 redirect(s), 742 ms total
Info::
Single redirect
Got: https://engadget.com → https://www.engadget.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 742 ms total
Got: 742 ms

https://engadget.com

156 ms · HTTP/1.1

301

https://www.engadget.com/

585 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://engadget.com301156 msHTTP/1.1ATS
2https://www.engadget.com/200585 msHTTP/1.1ATS

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
engadget.com — via MarkMonitor Inc., 22 years, 6 months old, hosted on AWS
PASS
engadget.com — via MarkMonitor Inc., 22 years, 6 months old, hosted on AWS
Info::
Domain registered until Jan 23, 2027 (9 months 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: MarkMonitor 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: AWS
Got: AS16509
Domain expiry

222 days

January 23, 2027

SSL certificate

154 days

Issued by DigiCert Inc

Domain age

22 years, 6 months

Registered January 23, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.248.158.7

Registrar

MarkMonitor Inc.

Unlocked 5 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 MarkMonitor Inc.
Created January 23, 2004 (22 years, 6 months ago)
Expires January 23, 2027 (9 months)
Last Updated December 22, 2025
Name Servers ns1.yahoo.com, ns2.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns5.yahoo.com
DNSSEC Not enabled
Hosting
IP Address 13.248.158.7
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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 189 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
36 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
101 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
190 ms
Total Time Total request time from DNS lookup through full response.
190 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 1 ms TLS Handshake 101 ms Server Processing 52 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