Resultados oficiales de juegos de azar en argentina ...

notitimba.com
  • Domain Name
    notitimba.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #48893
  • Page Size
    13.2 KB
  • Ip Address
    200.80.52.18
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    7 GIF, 2 JPG, 2 PNG

Website Meta Analysis

  • Title
    NotiTimba (®) Punto Com - quiniela en vivo - plus, poceada, borratina, megabola, mendoza, santa fe, santiago, cordoba, montevideo
  • Meta Keyword
    quiniela, quiniela plus, quiniela poceada, tombola, montevideo, loto, loto 5, quini 6, prode, brinco, telekino, mono bingo, toto bingo, mi bingo, borratina, quiniela provincia, quiniela nacional, quiniela mendoza, quiniela santa fe, quiniela cordoba, quiniela santiago, megabola, juga con maradona, las burbujitas del dragon, historias cabuleras
  • Meta Description
    Resultados oficiales de juegos de azar en argentina

Technical Analysis

  • Webserver
    Apache/2
  • Ip Address
    200.80.52.18
  • Domain Age
    9 Years, 4 Months, 3 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 08 Mar 2013 07:37:30 GMT
  • server: Apache/2
  • x-powered-by: PHP/5.2.14
  • expires: Mon,26 Jul 1997 05:00:00 GMT
  • cache-control: no-cache, must-revalidate
  • pragma: no-cache
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 3381
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for notitimba.com

IP 200.80.52.18 Analysis

  • Country Code
    AR
  • Country Code3
    ARG
  • Country Name
    Argentina
  • City
    Mendoza
  • Continent Code
    SA
  • Latitude
    32.8833
  • Longitude
    68.8167

  • % Joint Whois - whois.lacnic.net
    % This server accepts single ASN, IPv4 or IPv6 queries

    % LACNIC resource: whois.lacnic.net


    % Copyright LACNIC lacnic.net
    % The data below is provided for information purposes
    % and to assist persons in obtaining information about or
    % related to AS and IP numbers registrations
    % By submitting a whois query, you agree to use this data
    % only for lawful purposes.
    % 2013-02-23 00:16:04 (BRT -03:00)

    inetnum: 200.80.0/18
    status: allocated
    aut-num: N/A
    owner: IFX NETWORKS COLOMBIA
    ownerid: CO-IFNE-LACNIC
    responsible: Ezequiel Carson
    address: CARRERA 69 # 43B-44 OF. 501, N/A, N/A
    address: 57111 - BOGOTA - DC
    country: CO
    phone: +57 1 3693000 [1301]
    owner-c: IFC
    tech-c: IFC
    abuse-c: IFC
    inetrev: 200.80.52/24
    nserver: NS0.IFXNETWORKS.COM
    nsstat: 20130221 AA
    nslastaa: 20130221
    nserver: NS1.IFXNETWORKS.COM
    nsstat: 20130221 AA
    nslastaa: 20130221
    remarks: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
    created: 20010717
    changed: 20121008

    nic-hdl: IFC
    person: IFX NETWORKS COLOMBIA
    e-mail: ipadmin@IFXCORP.COM
    address: Autopista Norte # 114 - 78 Oficina 201, n/a, n/a
    address: 57111 - BOGOTA - DC
    country: CO
    phone: +57 1 3693000 []
    created: 20021021
    changed: 20120911

    % whois.lacnic.net accepts only direct match queries.
    % Types of queries are: POCs, ownerid, CIDR blocks, IP
    % and AS numbers.

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 15 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.7357068990988329
Message Error
  • Error Line 8, Column 6: document type does not allow element "HEAD" here
    <head>

    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 10, Column 56: required attribute "TYPE" not specified
    	<script src="http://www.notitimba.com/comn/js/swfs.js"></script>

    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>.

  • Error Line 47, Column 7: end tag for "HEAD" which is not finished
    </head>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 49, Column 21: there is no attribute "ONSELECTSTART"
    <body onselectstart="return false" oncopy="return false" oncontextmenu="return …

    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 49, Column 43: there is no attribute "ONCOPY"
    …y onselectstart="return false" oncopy="return false" oncontextmenu="return fal…

    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 49, Column 72: there is no attribute "ONCONTEXTMENU"
    …nselectstart="return false" oncopy="return false" oncontextmenu="return false">

    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.

Visitor Analysis

Daily Visitor
  • 4.433 visits
Daily Visitor