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
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
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
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
<html>
<head>
<META NAME="robots" CONTENT="noindex,nofollow">
<script src="/_Incapsula_Resource?SWJIYLWA=5074a744e2e3d891814e9a2dace20bd4,719d34d31c8e3a6e6fffd425f7e032f3">
</script>
<body>
</body></html>
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations64 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 Records1 A records, 84 ms lookupPASS
| A | 107.154.75.234 |
| AAAA | — |
| CNAME | — |
| NS | ns3.g10.cfdns.info, ns4.g10.cfdns.co.uk, ns2.g10.cfdns.biz, ns1.g10.cfdns.net |
| MX | 10 us-smtp-inbound-1.mimecast.com 10 us-smtp-inbound-2.mimecast.com |
| TXT | google-site-verification=XNwr-iT-a9W0Qla5sktYUJY5rY_9ogSUXCiLuk7a1cc mandrill_verify.DK9hgBSbpLqLn30AdWPUcA mandrill_verify.mClDOLYp5EPZ0ZFszatr0A Slz3SA13zRqMoYtogaBowFm0ypFx4rwaSSwcHcqBe788+MN4aWpK23ReyfuZ+2+f/HMulKpftRul2oVb... apple-domain-verification=XcG2zPcqdG6aWGpj MS=ms86668286 al4lnb90g2ei2vekg9lkb0oe1c m3rvlm0h3i4i9qkcvaf1cattks t9obvgugjv5kai0pi3febsckk6 XxLTj5SgsdxVLxMvyxSJx1bDV0GOclJpFYlGiC+tuwKEN4gFTVpMxFzXXl4OemYAnzPYjLn5LHjfnvXF... _globalsign-domain-verification=Us09jNjjDPAWyhJ-7fCdXO4a1iN3O06oqXODwXxXq7 google-site-verification=wlB077lxpLz7NWmM59QFbwEW5LWoheUYVTVT8ZHaxvg globalsign-domain-verification=B840B3D1734FE088B4D229888C40E2D1 facebook-domain-verification=3fnzvntxz33073c9gxc6fwsiwdkgfm SPF v=spf1 include:spf.protection.outlook.com include:_netblocks.mimecast.com a:hybr... globalsign-domain-verification=9471429DBEEA952FE77C96FAA0DE0799 960veh2fc21v4i200lm5ng985n |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 390 ms totalPASS
https://dailyherald.com
291 ms · HTTP/1.1
https://www.dailyherald.com/
100 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://dailyherald.com | 301 | 291 ms | HTTP/1.1 | |
| 2 | https://www.dailyherald.com/ | 200 | 100 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligencedailyherald.com — via Network Solutions, LLC, 31 years, 6 months old, hosted on INCAPSULA - Incapsula Inc, USPASS
1370 days
March 15, 2030
64 days
Issued by GlobalSign nv-sa
31 years, 6 months
Registered March 14, 1995
Not enabled
Protects against DNS spoofing
INCAPSULA - Incapsula Inc, US
ASN AS19551
107.154.75.234
Network Solutions, 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