Conheça o maior banco do mundo. Seja um cliente do banco HSBC e aproveite todos os produtos e serviços financeiros que só o maior banco do mundo pode oferecer. Acesse: hsbc.com.br ...

hsbc.com.br
  • Domain Name
    hsbc.com.br
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #5180
  • Page Size
    25.4 KB
  • Ip Address
    200.152.233.40
  • Heading
    H1: 1, H2: 0, H3: 4, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 3 JPG, 0 PNG

Website Meta Analysis

  • Title
    HSBC Bank Brasil S.A. - Banco Múltiplo
  • Meta Keyword
    banco, hsbc, credito parcelado, internet bank, hsbc premier, Conta Corrente, Empréstimos, Financiamentos, Cartões de Crédito, Investimentos, Capitalização, Seguros, Previdência, Consórcios
  • Meta Description
    Conheça o maior banco do mundo. Seja um cliente do banco HSBC e aproveite todos os produtos e serviços financeiros que só o maior banco do mundo pode oferecer. Acesse: hsbc.com.br

Technical Analysis

  • Webserver
    IBM_HTTP_Server
  • Ip Address
    200.152.233.40
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from hsbc.com.br.

HTML Analysis

  • date: Thu, 28 Feb 2013 19:03:50 GMT
  • server: IBM_HTTP_Server
  • ibm-web2-location: /1/2/!ut/p/c5/04_SB8K8xLLM9MSSzPy8xBz9CP0os3gDd-NQv1BDg2AXA1-PEE_zIDcTAwgAykcC5XEARwMCuv088nNT9QtyI8oBxbnFNQ!!/dl3/d3/L2dBISEvZ0FBIS9nQSEh/
  • content-location: /1/2/!ut/p/c5/04_SB8K8xLLM9MSSzPy8xBz9CP0os3gDd-NQv1BDg2AXA1-PEE_zIDcTAwgAykcC5XEARwMCuv088nNT9QtyI8oBxbnFNQ!!/dl3/d3/L2dBISEvZ0FBIS9nQSEh/
  • cache-control: no-cache, no-store, must-revalidate
  • expires: Thu, 01 Jan 1970 00:00:00 GMT
  • pragma: no-cache
  • vary: User-Agent,Cookie,Accept-Encoding
  • s: hbbr-vhim65e
  • content-encoding: gzip
  • content-type: text/html; charset=UTF-8
  • content-language: en-US
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for hsbc.com.br

IP 200.152.233.40 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 200.152.233.40

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 9 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.7224191063174115
Message Error
  • Warning Line 226, Column 18: character "&" is the first character of a delimiter but occurred as data
    		if (keynum==13 && enter==0){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 226, Column 19: character "&" is the first character of a delimiter but occurred as data
    		if (keynum==13 && enter==0){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 234, Column 52: character "&" is the first character of a delimiter but occurred as data
    ….getElementById('search').value != '' && (document.getElementById('search').va…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 234, Column 53: character "&" is the first character of a delimiter but occurred as data
    …getElementById('search').value != '' && (document.getElementById('search').val…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 234, Column 113: character "&" is the first character of a delimiter but occurred as data
    …ById('search').value != 'Procurar...' && document.getElementById('search').val…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 234, Column 114: character "&" is the first character of a delimiter but occurred as data
    …yId('search').value != 'Procurar...' && document.getElementById('search').valu…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 246, Column 129: cannot generate system identifier for general entity "queryString"
    …-pesquisa?searchRequest=searchRequest&queryString=" onsubmit="return RemoveSpe…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 246, Column 129: general entity "queryString" not defined and no default entity
    …-pesquisa?searchRequest=searchRequest&queryString=" onsubmit="return RemoveSpe…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 246, Column 140: reference not terminated by REFC delimiter
    …earchRequest=searchRequest&queryString=" onsubmit="return RemoveSpecialCharact…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 246, Column 140: reference to external entity in attribute value
    …earchRequest=searchRequest&queryString=" onsubmit="return RemoveSpecialCharact…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 246, Column 140: reference to entity "queryString" for which no system identifier could be generated
    …earchRequest=searchRequest&queryString=" onsubmit="return RemoveSpecialCharact…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 246, Column 128: entity was defined here
    …a-pesquisa?searchRequest=searchRequest&queryString=" onsubmit="return RemoveSp…
  • Error Line 253, Column 67: there is no attribute "alt"
    			title="Clique aqui para iniciar a pesquisa" class="button" alt="Clique

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 493, Column 7: document type does not allow element "tr" here; assuming missing "table" start-tag
    			<tr>
  • Error Line 588, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 493, Column 4: start tag was here
    			<tr>
  • Warning Line 619, Column 115: cannot generate system identifier for general entity "WT.ac"
    …on/html/hsbc-online.shtml?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Sol…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 619, Column 115: general entity "WT.ac" not defined and no default entity
    …on/html/hsbc-online.shtml?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Sol…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 619, Column 120: reference not terminated by REFC delimiter
    …ml/hsbc-online.shtml?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Solicite…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 619, Column 120: reference to external entity in attribute value
    …ml/hsbc-online.shtml?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Solicite…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 619, Column 120: reference to entity "WT.ac" for which no system identifier could be generated
    …ml/hsbc-online.shtml?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Solicite…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 619, Column 114: entity was defined here
    …mon/html/hsbc-online.shtml?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="So…
  • Warning Line 619, Column 133: cannot generate system identifier for general entity "produto"
    …e.shtml?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Solicite agora"> <img…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 619, Column 133: general entity "produto" not defined and no default entity
    …e.shtml?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Solicite agora"> <img…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 619, Column 140: reference not terminated by REFC delimiter
    …?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Solicite agora"> <img src="/…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 619, Column 140: reference to external entity in attribute value
    …?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Solicite agora"> <img src="/…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 619, Column 140: reference to entity "produto" for which no system identifier could be generated
    …?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Solicite agora"> <img src="/…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 619, Column 132: entity was defined here
    …ne.shtml?qs_id=QS047&WT.ac=HBBR_PIDS01&produto=CP" title="Solicite agora"> <im…
  • Warning Line 720, Column 204: reference not terminated by REFC delimiter
    …s/twitter-sac.html?wt.ac=HBBR_ATCA&amp','WT.ti','HSBC%20Atende');" target="_bl…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

Visitor Analysis

Daily Visitor
  • 31.500 visits
Daily Visitor