Domain intelligence
Security Report for
A closer look at this domain’s security, infrastructure, and public records. Findings first, with the evidence behind every result.
Explore the reportWebsite Security
HTTPS, browser protections, DNS controls and known threats
Strong website security
The public security settings RequestGuard checked are well configured.
Secure connection
Strong40/40
Browser protections
Needs work24/30
Domain protection
Strong15/15
Known threats
Strong15/15
Fix these first
- 1
Content security policy
4/10To earn 10/10, remove *, http:, https:, data:, 'unsafe-inline', and 'unsafe-eval' from script-src or its default-src fallback. Allow exact hosts and use per-request nonces or hashes for required inline scripts.
Strongest results
-
HTTPS response
15/15HTTPS returned status 403.
-
Valid TLS certificate
10/10The TLS certificate is valid for this domain.
-
DNSSEC
8/8DNSSEC validation data was found.
All 15 security checks
Every result is shown, with what it means and how to fix it.
HTTPS response
HTTPS returned status 403.
Valid TLS certificate
The TLS certificate is valid for this domain.
HTTP redirects to HTTPS
HTTP redirects to HTTPS.
Modern TLS
TLSv1.3 was negotiated.
Strict transport security
Strict-Transport-Security covers at least 180 days.
Content security policy
Content-Security-Policy is enforced but allows broad script sources.
To earn 10/10, remove *, http:, https:, data:, 'unsafe-inline', and 'unsafe-eval' from script-src or its default-src fallback. Allow exact hosts and use per-request nonces or hashes for required inline scripts.
Frame protection
The response limits which sites may frame it.
Content type protection
Content type sniffing is disabled.
Referrer policy
Referrer-Policy uses same-origin.
Browser permissions policy
Common sensitive browser capabilities are disabled by default.
DNSSEC
DNSSEC validation data was found.
Certificate authority restriction
CAA records restrict certificate issuance.
Known malware reports
No active malware-distribution URL was reported.
Threat-blocking DNS
3 threat-protection resolvers returned the domain.
Domain blocklists
The domain did not match the checked domain blocklists.
This dated automated check does not verify the business, its content, or every page. The score describes the configuration observed during this scan.
Badges and embed code
Embed code
<a href="https://requestguard.com/domain/llmbase.ai/">
<img src="https://requestguard.com/domain/llmbase.ai/badges/security.svg" alt="Website security grade for llmbase.ai" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a> Embed code
<a href="https://requestguard.com/domain/llmbase.ai/#infrastructure">
<img src="https://requestguard.com/domain/llmbase.ai/badges/location.svg" alt="Network location for llmbase.ai" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a> Embed code
<a href="https://requestguard.com/domain/llmbase.ai/">
<img src="https://requestguard.com/domain/llmbase.ai/badges/trust.svg" alt="Trust badge for llmbase.ai" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a> Embed code
<a href="https://requestguard.com/domain/llmbase.ai/#whois">
<img src="https://requestguard.com/domain/llmbase.ai/badges/domain-rating.svg" alt="Domain Rating for llmbase.ai" width="160" height="44" loading="lazy" decoding="async" fetchpriority="low">
</a> API requests require a workspace key and a plan with Lookups access.
The hosted badge updates after a manual scan. A downloaded badge stays static and avoids contacting RequestGuard on page views.
Search visibility
Homepage signals that can affect crawling and indexing
Obstacles found
The crawler found technical obstacles that may prevent access or indexing. Start with the flagged checks below.
6 homepage checks · Unscored
Observed request
Automated crawler access
a Cloudflare browser challenge was served instead of the public homepage (HTTP 403).
Review the hosting firewall or bot-protection rules. Public pages should not require a JavaScript challenge, and verified search crawlers should be exempt from automated challenges.
Indexing directives
A browser challenge was returned instead of the homepage, so its robots metadata could not be checked.
robots.txt homepage rule
No robots.txt rule blocking Googlebot from the homepage was found.
Canonical URL
A browser challenge was returned instead of the homepage, so its canonical URL could not be checked.
Search-readable HTML
The sampled response contains a Cloudflare browser challenge, not the public page content.
Serve the public HTML to crawlers without requiring a JavaScript security challenge.
Sitemap discovery
robots.txt declares 1 sitemap.
This is not a Google index lookup. RequestGuard tests public signals with an identified automated crawler. Only URL Inspection for a verified Google Search Console property can confirm Google's last crawl, selected canonical, and indexing decision.
Open Google's URL Inspection guideCached result
Public exposure
Sensitive files and public administrative interfaces
Not checked—run a website scan.
Checks 100 common paths and up to 50 technology-specific paths. Opening this report does not start exposure checks.
These are bounded, unauthenticated crawler observations, not a penetration test. A public login is not automatically a vulnerability. Secret values are discarded. Findings do not affect your security score.
Server Infrastructure
Resolved addresses, networks, and hosting providers
DNS Records
A, AAAA, MX, and resolving certificate hostnames, with other record types on demand
Email & DNS Security
MX, SPF, DMARC, DNSSEC, and CAA posture
WHOIS & Registrar
Registration details via RDAP
Registered 1.2 years ago
Registration history and published ownership records. Domain age and Domain Rating are context, not a security verdict.
Registrar
Registration dates
Domain age
1.2 years
Created
Jul 7, 2025
Updated
Sep 11, 2026
Expires
Jul 7, 2027
Registrant
Domain status
Registry status codes — green means the owner locked out unauthorized changes
Checked
Reputation & DNS filtering
Resolver behavior, domain datasets, and server-IP evidence
Resolver summary
No match found in 3 checked threat-protection resolvers.
Checked . No-match results apply only to the sources that returned comparable evidence.
Resolver filtering records provider behavior. It does not by itself prove that a domain is malicious.
Resolver matrix
Five public filtering policies compared with neutral DNS
Threat protection
Malware and phishing policy
Ads & tracking
Mixed privacy and security policy
Family / content
Content and security policy
Reputation datasets
URL and domain-list evidence, separate from resolver policy
Reported malware-distribution URLs
URLhaus metadata; this is not a direct SURBL query
URLhaus metadata; this is not a direct Spamhaus DBL query
Server-IP DNSBL checks & threat feeds
104.26.15.60
DNSBL and network-feed matches do not determine the domain verdict. Shared hosting, reverse proxies, and CDNs can put unrelated domains on the same address.
Barracuda
b.barracudacentral.org
SpamCop
bl.spamcop.net
UCEPROTECT L1
dnsbl-1.uceprotect.net
DroneBL
dnsbl.dronebl.org
NextDNS and other custom profiles are not tested because their result depends on enabled lists, security settings, and parental controls. Check the provider log for the exact rule.
Cached result