Amantes & Cia   Este site contém material orientado sexualmente para adultos e destinado a indivíduos MAIORES DE 18 ANOS. Se este tipo de material ofende você, ou ainda se você está acessando ...

amantesecia.com.br
  • Domain Name
    amantesecia.com.br
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #148048
  • Page Size
    4.1 KB
  • Ip Address
    187.45.240.114
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 1, H6: 0
  • Images
    0 GIF, 0 JPG, 1 PNG

Website Meta Analysis

  • Title
    Amantes & Cia
  • Meta Keyword
  • Meta Description
    Amantes & Cia   Este site contém material orientado sexualmente para adultos e destinado a indivíduos MAIORES DE 18 ANOS. Se este tipo de material ofende você, ou ainda se você está acessando a internet de algum país ou localidade onde este ...

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    187.45.240.114
  • Domain Age
    12 Years, 9 Months, 17 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 03 Oct 2013 04:04:34 GMT
  • server: Apache
  • connection: close
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for amantesecia.com.br

DNS Analysis


DNS servers
ns1.locaweb.com.br [189.126.108.2]
ns2.locaweb.com.br [201.76.40.2]


DNS Records

Answer records
amantesecia.com.br A 187.45.240.114 3600s
amantesecia.com.br NS  ns3.locaweb.com.br 3600s
amantesecia.com.br MX
preference: 10
exchange: mx.b.locaweb.com.br
3600s
amantesecia.com.br MX
preference: 20
exchange: mx.jk.locaweb.com.br
3600s
amantesecia.com.br NS  ns1.locaweb.com.br 3600s
amantesecia.com.br SOA
server: ns1.locaweb.com.br
email: postmaster@locaweb.com.br
serial: 2009070101
refresh: 3600
retry: 600
expire: 1209600
minimum ttl: 3600
3600s
amantesecia.com.br MX
preference: 10
exchange: mx.a.locaweb.com.br
60s
amantesecia.com.br TXT v=spf1 include:_spf.locaweb.com.br ?all 3600s
amantesecia.com.br NS  ns2.locaweb.com.br 3600s

Authority records

Additional records

IP 187.45.240.114 Analysis

  • Country Code
    BR
  • Country Code3
    BRA
  • Country Name
    Brazil
  • City
    S�o Paulo
  • Continent Code
    SA
  • Latitude
    23.5333
  • Longitude
    46.6167
  • No whois ip data for 187.45.240.114

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 12 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.40288620771232553
Message Error
  • Error Line 1, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Error Line 5, Column 8: required attribute "TYPE" not specified
    <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>.

  • Warning Line 17, Column 93: NET-enabling start-tag requires SHORTTAG YES
    …site-verification" content="NgagdyMYWflwbYxeCGwhYTejutaQu859IdOqWP8hhMg" /><br>

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

    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 17, Column 98: document type does not allow element "BR" here
    …site-verification" content="NgagdyMYWflwbYxeCGwhYTejutaQu859IdOqWP8hhMg" /><br>

    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 28, Column 83: there is no attribute "LEFTMARGIN"
    …="#ffFF00" alink="#FFFF00" leftmargin="0" topmargin="0" marginwidth="0" margin…

    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 28, Column 97: there is no attribute "TOPMARGIN"
    … alink="#FFFF00" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">

    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 28, Column 113: there is no attribute "MARGINWIDTH"
    … alink="#FFFF00" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">

    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 28, Column 130: there is no attribute "MARGINHEIGHT"
    … alink="#FFFF00" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">

    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 32, Column 62: required attribute "ALT" not specified
      <p><img name="Amantes" src="images/logo_png.png" border="0"> 

    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 76, Column 31: end tag for "B" omitted, but its declaration does not permit this
                Entrar </a> </font> </b></font></div>
    • You forgot to close a tag, or
    • you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.

    The next message, "start tag was here" points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

  • Info Line 74, Column 30: start tag was here
            de 18 anos</b></font><b><br>
  • Error Line 76, Column 36: end tag for element "B" which is not open
                Entrar </a> </font> </b></font></div>

    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 76, Column 43: end tag for element "FONT" which is not open
                Entrar </a> </font> </b></font></div>

    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
  • 1.283 visits