Anuncios clasificados de compra venta en Estados Unidos. Publica tus anuncios y fotos GRATIS y sin tener que registrarte. ...

clasificados.st
  • Domain Name
    clasificados.st
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #25097
  • Page Size
    15.2 KB
  • Ip Address
    174.36.12.82
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    anuncios de Compra Venta en Estados Unidos. Clasificados .ST
  • Meta Keyword
    anuncios,clasificados,venta,vendo,compra,compro,avisos,auto,coche,moto,computadora,ordenador,movil,celular
  • Meta Description
    Anuncios clasificados de compra venta en Estados Unidos. Publica tus anuncios y fotos GRATIS y sin tener que registrarte.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    174.36.12.82
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from clasificados.st.

HTML Analysis

  • date: Thu, 19 Sep 2013 13:49:55 GMT
  • server: Apache
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.2.13
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate
  • pragma: no-cache
  • content-encoding: gzip
  • content-length: 4092
  • connection: close
  • content-type: text/html; charset=ISO-8859-1
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for clasificados.st

DNS Analysis


DNS servers
ns2.clasificados.st [174.36.13.244]
ns1.clasificados.st [174.36.12.82]


DNS Records

Answer records
clasificados.st A 174.36.12.82 14400s
clasificados.st SOA
server: clasificados.st
email: dns@clasificados.st
serial: 2011052501
refresh: 10800
retry: 7200
expire: 14400
minimum ttl: 3600
14400s
clasificados.st NS  ns1.clasificados.st 14400s
clasificados.st NS  ns2.clasificados.st 14400s
clasificados.st MX
preference: 1
exchange: smtp.clasificados.st
14400s
clasificados.st TXT v=spf1 mx ip4:174.36.12.82 mx:smtp.clasificados.st ~all 14400s

Authority records

Additional records
ns1.clasificados.st A 174.36.12.82 14400s
ns2.clasificados.st A 174.36.13.244 14400s
smtp.clasificados.st A 174.36.12.82 14400s

IP 174.36.12.82 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Dallas
  • Continent Code
    75207
  • Latitude
    214
  • Longitude
    623
  • %rwhois V-1.5:003fff:00 rwhois.softlayer.com (by Network Solutions, Inc. V-1.5.9.5)
    network:Class-Name:network
    network:ID:NETBLK-SOFTLAYER.174.36.0.0/18
    network:Auth-Area:174.36.0.0/18
    network:Network-Name:SOFTLAYER-174.36.0.0
    network:IP-Network:174.36.12.80/29
    network:IP-Network-Block:174.36.12.80-174.36.12.87
    network:Organization;I:diezmil s.c.
    network:Street-Address:plaza parador 10
    network:City:Monforte del Cid
    network:Postal-Code:03670
    network:Country-Code:ES
    network:Tech-Contact;I:sysadmins@softlayer.com
    network:Abuse-Contact;I:adm.clasificados.st@gmail.com
    network:Admin-Contact;I:IPADM258-ARIN
    network:Created:2008-10-27 18:45:56
    network:Updated:2010-03-16 11:40:21
    network:Updated-By:ipadmin@softlayer.com

    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 8 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.509201667201026
Message Error
  • Warning Line 7, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …gle-site-verification" content="xPJkk2F2sEGKlOEJRlf6WpjJ4rYG0kUUUsvMqd-iGSc" />

    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 7, Column 94: character data is not allowed here
    …gle-site-verification" content="xPJkk2F2sEGKlOEJRlf6WpjJ4rYG0kUUUsvMqd-iGSc" />

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 38, Column 11: element "G:PLUSONE" undefined
    <g:plusone></g:plusone>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Warning Line 162, Column 627: cannot generate system identifier for general entity "p"
    …('http://us.clasificados.st/ayuda?t=5&p=3','Enlázanos',500,500)" style="color:…

    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 162, Column 627: general entity "p" not defined and no default entity
    …('http://us.clasificados.st/ayuda?t=5&p=3','Enlázanos',500,500)" style="color:…

    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.

  • Error Line 162, Column 628: reference to entity "p" for which no system identifier could be generated
    …'http://us.clasificados.st/ayuda?t=5&p=3','Enlázanos',500,500)" style="color:g…

    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 162, Column 626: entity was defined here
    …a('http://us.clasificados.st/ayuda?t=5&p=3','Enlázanos',500,500)" style="color…
  • Error Line 164, Column 119: reference to entity "p" for which no system identifier could be generated
    …'http://us.clasificados.st/ayuda?t=6&p=4','¿Quienes Somos?',450,400)">¿Quienes…

    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 162, Column 626: entity was defined here
    …a('http://us.clasificados.st/ayuda?t=5&p=3','Enlázanos',500,500)" style="color…
  • Error Line 168, Column 5: end tag for element "TD" which is not open
    </td></tr></table> 

    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 168, Column 10: end tag for element "TR" which is not open
    </td></tr></table> 

    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 168, Column 18: end tag for element "TABLE" which is not open
    </td></tr></table> 

    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.

Visitor Analysis

Daily Visitor
  • 5.250 visits