namesilo.com
Test complete··4.5s
4 critical·6 warnings·3 unmeasured
https://namesilo.com
- 4 fail
- 6 warn
- 0 info
Pipeline complete
Crawler access
public crawler identity × robots policy × HTTP delivery × usability
| agent | robots | http | usable | challenge | captcha | waf | bytes |
|---|---|---|---|---|---|---|---|
| Default HTTP Clientother | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| Googlebotsearch | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| Googlebot Smartphonesearch | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| Bingbotsearch | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| OAI-SearchBotai | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| GPTBotai | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| ClaudeBotai | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| Claude-Userai | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| PerplexityBotai | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| Perplexity-Userai | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| Applebotsearch | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| Applebot-Extendedai | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
| Common Crawlarchive | ? | 403 | ✕ | ! | ✕ | ! | 5,847 |
Raw versus rendered
JS dependency LOW
Fact parity
Visible HTML ↔ machine representations · status definitions
Fact ledger
3 subject · predicate · object
| subject | predicate | object | source | representation | assertion | recovery |
|---|---|---|---|---|---|---|
| https://namesilo.com | hasTitle | Attention Required! | Cloudflare | visible html | visible | explicit | |
| https://namesilo.com | hasHeading | Sorry, you have been blocked | visible html | visible | explicit | |
| Please | include | what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page | visible html | visible | explicit |
Structured data integrity
parse · serialization · graph identity · intent survives
No JSON-LD present in the initial HTML.
Entity identity
0 nodes · 0 relationships
No entity graph could be built from this page.
Critical fact byte depth
deeper = higher ingestion risk · what this measures
Measurement components
Leaf components that explain the composite. Null stays null. Glossary
Evidence
10 findings
fetchBot friction on fetchfail
- check
- FETCH-CHALLENGE
- confidence
- HIGH
- class
- BOT_CHALLENGE
- why
- Response looks like a challenge, WAF, or access wall
- interpretation
- Transport may succeed; content is not usable for ingestion
- url
- https://namesilo.com
- source
- http
- status
- 403
- observed
- 2026-09-30T13:14:06.446Z
<!DOCTYPE html> <!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]--> <!--[if IE 7]> <html class="no-js ie7 oldie" lang="en-US"> <![endif]--> <!--[if IE 8]> <html class="no-js ie8 oldie" lang="en-US"> <![endif]--> <!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]--> <head> <title>Attention Required! | Cloudflare</title> <meta charset="UTF-8" /> <meta
indexabilitynoindex presentfail
- check
- INDEX-NOINDEX
- confidence
- DETERMINISTIC
- class
- NOINDEX
- why
- noindex, nofollow
- url
- https://namesilo.com
- source
- meta
- observed
- 2026-09-30T13:14:10.906Z
No raw evidence payload attached.
indexabilityNon-indexable HTTP statefail
- check
- INDEX-STATUS
- confidence
- DETERMINISTIC
- class
- BOT_CHALLENGE
- why
- BOT_CHALLENGE
- url
- https://namesilo.com
- source
- http
- status
- 403
- observed
- 2026-09-30T13:14:10.906Z
No raw evidence payload attached.
salienceSALIENCE_CONFLICTfail
- check
- SALIENCE-CONFLICT
- confidence
- MEDIUM
- class
- SALIENCE_CONFLICT
- why
- Title "Attention Required! | Cloudflare" vs H1 "Sorry, you have been blocked" vs body "Please enable cookies. Sorry, you have been blocked You are unable to access nam" (no schema)
- url
- https://namesilo.com
- source
- raw html
- observed
- 2026-09-30T13:14:10.906Z
Please enable cookies. Sorry, you have been blocked You are unable to access namesilo.com Why have I been blocked? This website is using a security service to protect itself from online attacks. The a
schemaNo parseable JSON-LD graphwarn
- check
- SCHEMA
- confidence
- HIGH
- why
- Structured identity is missing for machines
- url
- https://namesilo.com
- source
- json ld
- observed
- 2026-09-30T13:14:06.460Z
No raw evidence payload attached.
canonicalMissing canonicalwarn
- check
- CANONICAL-MISSING
- confidence
- DETERMINISTIC
- why
- Page does not declare a canonical URL
- url
- https://namesilo.com
- source
- raw html
- observed
- 2026-09-30T13:14:10.905Z
No raw evidence payload attached.
robotsrobots.txt missing or unreadablewarn
- check
- ROBOTS-MISSING
- confidence
- DETERMINISTIC
- why
- HTTP 403 for https://namesilo.com/robots.txt
- url
- https://namesilo.com/robots.txt
- source
- robots
- status
- 403
- observed
- 2026-09-30T13:14:06.476Z
No raw evidence payload attached.
sitemapAudited URL not in sitemapwarn
- check
- SITEMAP
- confidence
- HIGH
- why
- https://namesilo.com missing from https://www.namesilo.com/sitemap.xml
- url
- https://www.namesilo.com/sitemap.xml
- source
- sitemap
- observed
- 2026-09-30T13:14:07.019Z
https://www.namesilo.com/ https://www.namesilo.com/support/v2 https://www.namesilo.com/domain/search-domains https://www.namesilo.com/domain/transfer-domains https://www.namesilo.com/Marketplace https://www.namesilo.com/pricing https://www.namesilo.com/whois https://www.namesilo.com/discounts-and-promotions https://www.namesilo.com/hosting https://www.namesilo.com/ssl https://www.namesilo.com/support/v2/articles/domain-manager/whois-privacy https://www.namesilo.com/email
sitemapDuplicate sitemap URLswarn
- check
- SITEMAP
- confidence
- HIGH
- why
- https://www.namesilo.com/pricing, https://www.namesilo.com/hosting, https://www.namesilo.com/account/billing-manager, https://www.namesilo.com/tld/biz
- url
- https://www.namesilo.com/sitemap.xml
- source
- sitemap
- observed
- 2026-09-30T13:14:07.020Z
No raw evidence payload attached.
renderRendering errorswarn
- check
- RENDER-ERROR
- confidence
- HIGH
- why
- desktop: Failed to load resource: the server responded with a status of 403 (); stateless: Failed to load resource: the server responded with a status of 403 (); mobile: Failed to load resource: the server responded with a status of 403 ()
- url
- https://namesilo.com
- source
- rendered dom
- observed
- 2026-09-30T13:14:10.906Z
desktop: Failed to load resource: the server responded with a status of 403 () stateless: Failed to load resource: the server responded with a status of 403 () mobile: Failed to load resource: the server responded with a status of 403 () mobile: %c%d font-size:0;color:transparent NaN
Developer handoff
Derived from 10 finding-backed tickets
Bot friction on fetch on /
Response looks like a challenge, WAF, or access wall
Expected — Machine-readable, consistent, first-HTML representation of the fact
From check FETCH-CHALLENGE · Inspect evidence →
No parseable JSON-LD graph on /
Structured identity is missing for machines
Expected — Machine-readable, consistent, first-HTML representation of the fact
From check SCHEMA · Inspect evidence →
Missing canonical on /
Page does not declare a canonical URL
Expected — Machine-readable, consistent, first-HTML representation of the fact
From check CANONICAL-MISSING · Inspect evidence →
robots.txt missing or unreadable on /
HTTP 403 for https://namesilo.com/robots.txt
Expected — Machine-readable, consistent, first-HTML representation of the fact
From check ROBOTS-MISSING · Inspect evidence →
Audited URL not in sitemap on /
https://namesilo.com missing from https://www.namesilo.com/sitemap.xml
Expected — Machine-readable, consistent, first-HTML representation of the fact
From check SITEMAP · Inspect evidence →
Duplicate sitemap URLs on /
https://www.namesilo.com/pricing, https://www.namesilo.com/hosting, https://www.namesilo.com/account/billing-manager, https://www.namesilo.com/tld/biz
Expected — Machine-readable, consistent, first-HTML representation of the fact
From check SITEMAP · Inspect evidence →
noindex present on /
noindex, nofollow
Expected — Machine-readable, consistent, first-HTML representation of the fact
From check INDEX-NOINDEX · Inspect evidence →
Non-indexable HTTP state on /
BOT_CHALLENGE
Expected — Machine-readable, consistent, first-HTML representation of the fact
From check INDEX-STATUS · Inspect evidence →
SALIENCE_CONFLICT on /
Title "Attention Required! | Cloudflare" vs H1 "Sorry, you have been blocked" vs body "Please enable cookies. Sorry, you have been blocked You are unable to access nam" (no schema)
Expected — Machine-readable, consistent, first-HTML representation of the fact
From check SALIENCE-CONFLICT · Inspect evidence →
Rendering errors on /
desktop: Failed to load resource: the server responded with a status of 403 (); stateless: Failed to load resource: the server responded with a status of 403 (); mobile: Failed to load resource: the server responded with a status of 403 ()
Expected — Machine-readable, consistent, first-HTML representation of the fact
From check RENDER-ERROR · Inspect evidence →