Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 2840 ms totalFIX
https://inquirer.net
747 ms · HTTP/1.1
https://www.inquirer.net/wp-signup.php?n...
1088 ms · HTTP/1.1
https://www.inquirer.net/
1005 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://inquirer.net | 302 | 747 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.inquirer.net/wp-signup.php?n... | 301 | 1088 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.inquirer.net/ | 200 | 1005 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
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
User-agent: *
Disallow: /wp-admin/
Disallow: /xmlrpc.php
Disallow: /feed-karera
Disallow: /feed-lotto
Disallow: /feed-full-horoscope
Disallow: /feed-karera-tips
Disallow: /bandera-custom-feed
Disallow: /custom-feed-pagesuite
Disallow: /4711/
User-agent: *
Disallow: /factiva*
Disallow: /61405*
Disallow: /.well-known*
User-agent: Petalbot
User-agent: GPTBot
Disallow: /
User-agent: facebookexternalhit
Crawl-delay: 10
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations60 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
BCDN & DeliveryCloudflare (BYPASS)REVIEW
A+DNS Records2 A records, 39 ms lookupPASS
| A | 172.66.175.5, 104.20.44.25 |
| AAAA | 2606:4700:10::6814:2c19, 2606:4700:10::ac42:af05 |
| CNAME | — |
| NS | dawn.ns.cloudflare.com, jay.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | google-site-verification=iclsJL576k2YzKuw4vqKeesL9H1KkYks62rB5C4mU3k google-site-verification=2Occsvh7XtuhFMN_uNnl3XaL7Lm2a1hpuPbVKrhWrBk tollbit-domain-verification=3e56295e7477d03e754d3ac2333330883532739c6174bc832a22... facebook-domain-verification=xbz352h1e2ui4gbzp0k47la9v6vx2m google-site-verification=4SuYiV92RkTRIUQmCD21iPZvs20hHGmAlOa_WcTXWpo sendinblue-code:be7642cc714e793a1e2e016116c33006 SPF v=spf1 a mx include:_spf.elasticemail.com include:_spf.google.com include:208186... google-site-verification=-Y_ycsrXo28eAzxOxnDhNtZJ_UB7VZ_28qp6s8nXdxM apple-domain-verification=ga2nyznDCrc5yErR google-site-verification=fA5pUhQAXZRg_iHYlMI9tZOkYEsfU2Gg_HYwik46WvU google-site-verification=olsaOqN7LTKOfvXL0gliBCSZrag5d2znH37_1EWkHrk have-i-been-pwned-verification=dweb_2b3gv0ag8gq8y8apn4ztm4sm |
| 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.
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Domain Intelligenceinquirer.net — via Network Solutions, LLC, 29 years, 1 months oldPASS
2201 days
July 28, 2032
60 days
Issued by Let's Encrypt
29 years, 1 months
Registered July 29, 1997
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:10::6814:2c19
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