Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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 & Recommendations215 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
A+DNS Records2 A records, 55 ms lookupPASS
| A | 23.21.202.96, 174.129.224.216 |
| AAAA | — |
| CNAME | — |
| NS | ns-1379.awsdns-44.org, ns-753.awsdns-30.net, ns-1641.awsdns-13.co.uk, ns-410.awsdns-51.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | facebook-domain-verification=dza4d3qbsb9ief1k857z4ejlqmpwkm ahrefs-site-verification_e79c43e8b729d28aac502a5647137b517464e5dd71fed60c0d52c98... globalsign-domain-verification=57YfMdgD9DldxdIvzy_Zet-1fFYngI9M8TPxyGiiBk SPF v=spf1 include:_spf.google.com ~all google-site-verification=a5PiuY29-LIPJzNJ7QWdjMyGXqQ5cxA67i3Vg1oo75A |
| 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), 958 ms totalPASS
https://medicaldaily.com
413 ms · HTTP/1.1
https://www.medicaldaily.com/
546 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://medicaldaily.com | 301 | 413 ms | HTTP/1.1 | Varnish |
| 2 | https://www.medicaldaily.com/ | 200 | 546 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 4 URLsPASS
User-agent: *
Disallow: /feeds/*
Disallow: /system/
Disallow: /rss/articles/specialcat/
Disallow: /addineyeV2l
Disallow: /eyeblaster
Disallow: /doubleclick
Disallow: /ads/sponsored
Disallow: /comment/*
Disallow: /search?q=*
Disallow: /search/site*
Disallow: /tool/logout*
Disallow: /corporate/newsletter/signup?*
Sitemap: https://www.medicaldaily.com/sitemap.xml
Sitemap: https://www.medicaldaily.com/googlenews.xml
A+Domain Intelligencemedicaldaily.com — via MarkMonitor Inc., 21 years, 8 months old, hosted on AWSPASS
129 days
November 18, 2026
215 days
Issued by Amazon
21 years, 8 months
Registered November 18, 2004
Not enabled
Protects against DNS spoofing
AWS
ASN AS14618
174.129.224.216
MarkMonitor Inc.
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