Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
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
# This file defines the rules for automatic computer programs on
# Bloglovin, so called "robots", "bots", "crawlers" or "search engines".
# Bots are allowed as long as these rules are followed:
# * Do not log in.
# * Do not register a user account.
# * Use a User-Agent HTTP header with a link to your site or a working
# e-mail address, so we can contact you if there is any problem.
# * Do not try to send messages to our users.
# * Follow the robots.txt rules in this file.
# The format of this file is described at http://www.robotstxt.org/
User-agent: *
Disallow:
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations31 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 Records3 A records, 51 ms lookupPASS
| A | 104.26.2.87, 104.26.3.87, 172.67.74.169 |
| AAAA | 2606:4700:20::681a:257, 2606:4700:20::ac43:4aa9, 2606:4700:20::681a:357 |
| CNAME | — |
| NS | olivia.ns.cloudflare.com, keaton.ns.cloudflare.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx2.googlemail.com 10 aspmx4.googlemail.com 10 aspmx5.googlemail.com 10 aspmx3.googlemail.com |
| TXT | SPF v=spf1 include:spf.protection.outlook.com include:_spf.google.com include:mail.z... pinterest-site-verification=b8d8eadd18fcbd6f68f868de42752f0b status-page-domain-verification=r01cfm3g7dfd google-site-verification=WhW2c3WW5w-d5AMfbRDpVWGptCl50pPCGYHHAgBr3KY admitad-verification: bcaa79bef2 ms-domain-verification=6991c19c-835b-48a9-bfc4-a43c66b0388f globalsign-domain-verification=FnXWfFjPqReOGiIH8ITAbUasqKxnix6ftvTUzPOKHF |
| 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), 679 ms totalPASS
https://bloglovin.com
413 ms · HTTP/1.1
https://www.bloglovin.com/
265 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://bloglovin.com | 301 | 413 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.bloglovin.com/ | 200 | 265 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (17 ms)PASS
A+Domain Intelligencebloglovin.com — via GoDaddy.com, LLC, 17 years, 9 months oldPASS
66 days
September 23, 2026
31 days
Issued by Google Trust Services
17 years, 9 months
Registered September 23, 2008
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:20::ac43:4aa9
GoDaddy.com, LLC
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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