Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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 & Recommendations180 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
A+DNS Records4 A records, 11 ms lookupPASS
| A | 108.157.142.80, 108.157.142.30, 108.157.142.77, 108.157.142.98 |
| AAAA | — |
| CNAME | — |
| NS | ns-1089.awsdns-08.org, ns-145.awsdns-18.com, ns-1618.awsdns-10.co.uk, ns-939.awsdns-53.net |
| MX | 1 medicalnewstoday-com.mail.protection.outlook.com |
| TXT | MS=ms46353610 MS=ms66481913 _globalsign-domain-verification=gxDZTHFxmg56fm5vMzUelQcu7UZSnIYHxvoZHAUJYR c85b6dabed7846b1e154ab13034b2144.medicalnewstoday.com faohc8qu5e3lr7skckic2cvjfn google-site-verification=1Xn1W1GJxe6Pjgh8zKj59_pmRycNsp-oRjAa_g_TPrI google-site-verification=7kYX9RrRzjWH0qSRLx0JRx-fFWA5t55RFlrpUc5k9cc google-site-verification=MDpghCeMQngwoJjCqwsd23fpEXxfROvOjEGdOFnQA84 google-site-verification=XwAJ8gS4ghfdIeug_ChZ83cRvm5_5CuC_pdS_74KFmw google-site-verification=mLovNHxFZkuB78n27bVJj1nTociFUrzz_X0G_bwmwXY google-site-verification=uxsvzvOCGqJ3k1UwCYrg2znY3xsCbBVBjXA1IqxpM0M google-site-verification=zDcdVQX19UcJF3au4Y9dufYQ21FmMiWrpw_ItoOOf5Q SPF v=spf1 include:_spf.google.com include:aspmx.sailthru.com include:spf.protection... |
| CAA | Lookup not available with standard resolver |
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), 220 ms totalPASS
https://medicalnewstoday.com
20 ms · HTTP/1.1
https://www.medicalnewstoday.com/
200 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://medicalnewstoday.com | 301 | 20 ms | HTTP/1.1 | AmazonS3 |
| 2 | https://www.medicalnewstoday.com/ | 200 | 200 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 2 URLsPASS
User-agent: Mediapartners-Google*
Disallow:
User-agent: Nutch
Crawl-delay: 5
Disallow:
User-agent: Slurp
Disallow: /*.gif$
Disallow: /*.jpg$
# --- Amazon / AWS crawlers (begin) ---
# AmazonAdbot is intentionally allowed (ad targeting — see HLMR-6504)
User-agent: AmazonAdbot
Disallow:
User-agent: Amazonbot
Disallow: /
User-agent: Amzn-SearchBot
Disallow: /
User-agent: Amzn-User
Disallow: /
User-agent: amazon-kendra
Disallow: /
User-agent: amazon-QBusiness
Disallow: /
User-agent: bedrockbot
Disallow: /
User-agent: aws-quick-on-behalf-of-
Disallow: /
User-agent: AmazonProductDiscoverybot
Disallow: /
User-agent: AmazonBuyForMe
Disallow: /
User-agent: AmazonSellerInitiatedListing
Disallow: /
User-agent: NovaAct
Disallow: /
# --- Amazon / AWS crawlers (end) ---
User-agent: *
Crawl-delay: 5
Disallow: /linkfwd.php
Disallow: /counters.php
# Wordpress Previews
Disallow: /articles/mnt-*
Disallow: /program/mnt-*
# API Routes
Disallow: /api/*
# Invalid URLs
Disallow: */null$
Disallow: */inline$
User-agent: GPTBot
Disallow: /
User-agent: Applebot-Extended
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: Bytespider
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: ClaudeBot
Disallow: /
User-agent: Diffbot
Disallow: /
User-agent: FacebookBot
Disallow: /
User-agent: Meta-ExternalAgent
Disallow: /
User-agent: omgili
Disallow: /
User-agent: Timpibot
Disallow: /
User-agent: Webzio-Extended
Disallow: /
User-agent: DDM-DCipher/1.0.7
Disallow: /
# Sitemaps
Sitemap: https://www.medicalnewstoday.com/sitemap.xml
# Widget Sampler
Disallow: /articles/widget-sampler
# Static Test Articles
Disallow: /test/
# Block AMP URLs
Disallow: /amp/
A+Domain Intelligencemedicalnewstoday.com — via GoDaddy Corporate Domains, LLC, 22 years, 9 months old, hosted on AWSPASS
143 days
November 5, 2026
180 days
Issued by Amazon
22 years, 9 months
Registered November 5, 2003
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
108.157.142.80
GoDaddy Corporate Domains, LLC
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