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.
BRedirect Chain1 redirect(s), 6379 ms totalREVIEW
https://einpresswire.com
2240 ms · HTTP/1.1
https://www.einpresswire.com/
4139 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://einpresswire.com | 301 | 2240 ms | HTTP/1.1 | nginx |
| 2 | https://www.einpresswire.com/ | 200 | 4139 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
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
BCrawlabilityrobots.txt present, sitemap with 562 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
User-agent: msnbot
Crawl-delay: 30
Disallow: /ajax/
Disallow: /account/
Disallow: /article-print/
Disallow: /rss_expired
Disallow: /newsletters
Disallow: /world-media-directory/edit
User-agent: Googlebot
Crawl-delay: 10
Disallow: /ajax/
Disallow: /account/
Disallow: /article-print/
Disallow: /rss_expired
Disallow: /newsletters
Disallow: /world-media-directory/edit
User-agent: *
Crawl-delay: 30
Disallow: /ajax/
Disallow: /account/
Disallow: /article-print/
Disallow: /rss_expired
Disallow: /newsletters
Disallow: /world-media-directory/edit
Sitemap: https://www.einpresswire.com/sitemap
Sitemap: https://www.einpresswire.com/sitemap-news
Sitemap: https://www.einpresswire.com/sitemap-list
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BHTTP Probe TimingTotal 1150 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations196 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, 188 ms lookupPASS
| A | 52.15.235.213 |
| AAAA | — |
| CNAME | — |
| NS | ns.newsmatics.com, ns5.newsmatics.com, ns3.newsmatics.com, ans.newsmatics.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | spf2.0/pra ?all SPF v=spf1 mx ip4:23.253.63.22 ip4:104.130.119.236 ip4:173.203.96.64 ip4:173.203.97.... google-site-verification=dySamoVwcooE76Qi7HxJ7lTI_eojPyLAuiVyybR_HlE google-site-verification=knXK9MsYYzIoF-eFXX9LqvSeV6XLuL_j7-0zkmvXKB8 google-site-verification=r2ixEd4UqI44BM-Ii9aewCghkTeN3tLCGCDiPgAKTDY google-site-verification=J5a0zcu-K4zXVkfmMBkWylj7q6Bi7tfvyWtgdLGbjIA google-site-verification=drq6rcOr9hkoyEdosqveNTvCyEWSFzj_FoN1-ssI5nU google-site-verification=E3MvrynNOLVvIsUGQSYZnzM2VTRiiXFC41ke9KWfQ20 |
| 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.
A+Domain Intelligenceeinpresswire.com — via GoDaddy.com, LLC, 17 years, 7 months old, hosted on AWSPASS
182 days
December 15, 2026
196 days
Issued by DigiCert Inc
17 years, 7 months
Registered December 15, 2008
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
52.15.235.213
GoDaddy.com, 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