Informatieve site van KBC Bank en KBC Verzekeringen. Toegang tot KBC-Online en meer dan 25 simulaties o.a. over beleggingsfondsen, woningkrediet, autolening, leasing en verzekeringen. ...

kbc.be
  • Domain Name
    kbc.be
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #10019
  • Page Size
    6.9 KB
  • Ip Address
    193.244.74.86
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    KBC Bank & Verzekering
  • Meta Keyword
    KBC, KBC Bank, KBC Verzekeringen, KBC-Online, bankieren, lenen, beleggen, betalen, sparen, kredieten, agent, preventie, internetbankieren, financiering, internationale verzekeringsbibliotheek, rentetarieven, ticket shop, jongeren, cjp, aandelen, asset management, autoverzekering, bankkaart, brandverzekering, deposito, documentair krediet, trade finance, buitenlandse handel, eurocard, fonds, futures & opties, gezinspolis, groepsverzekering, hypothecair, lening, investering, investment banking, jobs, kasbon, kaskrediet, kredietkaart, leasing, levensverzekering, maestro, obligatie, omnium, pensioen, proton, rechtsbijstand, reis, schuldsaldo, self banking, simulatie, spaarrekening, telefoonbankieren, termijn, rekening, vastgoed, verzekeringsbon, wonen, woning, zichtrekening, diefstal, erfenis, libor, euribor, eonia, abb, cera, kredietbank, almanij, visa, cirrus, employee benefits
  • Meta Description
    Informatieve site van KBC Bank en KBC Verzekeringen. Toegang tot KBC-Online en meer dan 25 simulaties o.a. over beleggingsfondsen, woningkrediet, autolening, leasing en verzekeringen.

Technical Analysis

  • Webserver
  • Ip Address
    193.244.74.86
  • Domain Age
    15 Years, 3 Months, 16 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from kbc.be.

HTML Analysis

  • content-language: en-US
  • content-length: 6811
  • content-type: text/html; charset=UTF-8
  • date: Wed, 28 Aug 2013 04:56:01 GMT
  • p3p: CP="NON CUR OTPi OUR NOR UNI"
  • cache-control: no-cache="set-cookie, set-cookie2"
  • expires: Thu, 01 Dec 1994 16:00:00 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Domain Name: kbc
Domain Status: REGISTERED
Created: Mon Jun 1 1998
Registrant:
Not shown, please visit www.dns.be for webbased whois.
Registrar:
Domain Name: COMBELL GROUP NV
Website: www.combell.com
Name Servers:
ns2.kbc.be (193.245.3.200)
ns.kbc.be (193.244.76.200)

DNS Analysis


DNS servers
ns.kbc.be [193.244.76.200]
ns2.kbc.be


DNS Records

Answer records
kbc.be A 193.244.74.86 14400s
kbc.be MX
preference: 10
exchange: mail11.mailinfra.com
900s
kbc.be MX
preference: 10
exchange: mail12.mailinfra.com
900s
kbc.be SOA
server: ns.kbc.be
email: tech@kbc.be
serial: 2010090988
refresh: 1800
retry: 900
expire: 604800
minimum ttl: 900
14400s
kbc.be TXT v=spf1 mx ~all 14400s
kbc.be NS  ns2.kbc.be 14400s
kbc.be NS  ns.kbc.be 14400s

Authority records

Additional records

IP 193.244.74.86 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 5 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.4409193457416808
Message Error
  • Warning Line 19, Column 219: NET-enabling start-tag requires SHORTTAG YES
    …over beleggingsfondsen, woningkrediet, autolening, leasing en verzekeringen."/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 20, Column 921: NET-enabling start-tag requires SHORTTAG YES
    …bor, eonia, abb, cera, kredietbank, almanij, visa, cirrus, employee benefits"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 20, Column 921: document type does not allow element "META" here
    …bor, eonia, abb, cera, kredietbank, almanij, visa, cirrus, employee benefits"/>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 102, Column 7: end tag for element "HEAD" which is not open
    </head>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 103, Column 105: document type does not allow element "BODY" here
    …nk="#595959" alink="#595959" vlink="#595959" onLoad="onLoad();">			    								

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 108, Column 83: there is no attribute "ONERROR"
    …ps://www.kbc.be/PBL/nextgen/page/preprocessing/spacer.gif" onerror="noSSL();"/>

    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.

  • Warning Line 108, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …ps://www.kbc.be/PBL/nextgen/page/preprocessing/spacer.gif" onerror="noSSL();"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 108, Column 93: required attribute "ALT" not specified
    …ps://www.kbc.be/PBL/nextgen/page/preprocessing/spacer.gif" onerror="noSSL();"/>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

Visitor Analysis

Daily Visitor
  • 17.967 visits