LOGIN   CONT NOU   QUICKLIST 0  Video & Imagini  •  Articole  •  Gura lumii  3:57 Pot sa ma arunc de pe blocul dumneavoastra? de continental in Amuzant acum 1 ora si 55 minute ...

peteava.ro
  • Domain Name
    peteava.ro
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #25794
  • Page Size
    73.8 KB
  • Ip Address
    31.14.11.66
  • Heading
    H1: 0, H2: 0, H3: 3, H4: 15, H5: 0, H6: 0
  • Images
    44 GIF, 0 JPG, 1 PNG

Website Meta Analysis

  • Title
    PeTeava.Ro
  • Meta Keyword
  • Meta Description
    LOGIN   CONT NOU   QUICKLIST 0  Video & Imagini  •  Articole  •  Gura lumii  3:57 Pot sa ma arunc de pe blocul dumneavoastra? de continental in Amuzant acum 1 ora si 55 minute 34 0 0 1:23 Adauga la Quicklist Gandacul pacalit de vuple de continental ...

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    31.14.11.66
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from peteava.ro.

HTML Analysis

  • server: nginx
  • date: Wed, 30 Jan 2013 11:29:22 GMT
  • content-type: text/html
  • connection: keep-alive
  • x-powered-by: PHP/5.3.6-13ubuntu3.3
  • expires: Wed, 30 Jan 2013 11:29:21 GMT
  • cache-control: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for peteava.ro

DNS Analysis


DNS servers
ns1.chroot.ro [89.36.93.66]
ns2.chroot.ro [66.23.231.215]


DNS Records

Answer records
peteava.ro A 31.14.11.16 300s
peteava.ro A 31.14.11.66 300s
peteava.ro TXT v=spf1 ip4:188.241.12.0/23 ip4:86.105.155.0/24 ip4:31.14.11.0/24 ~all 86400s
peteava.ro SOA
server: ns1.chroot.ro
email: contact@chroot.ro
serial: 2013012602
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
peteava.ro NS  ns1.chroot.ro 86400s
peteava.ro NS  ns2.chroot.ro 86400s
peteava.ro MX
preference: 0
exchange: mail.peteava.ro
86400s

Authority records

Additional records
ns1.chroot.ro A 89.36.93.66 14400s
ns2.chroot.ro A 66.23.231.215 14400s
mail.peteava.ro A 31.14.11.67 86400s

IP 31.14.11.66 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 34 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.7324215649965611
Message Error
  • Error Line 60, Column 5: "if" is not a reserved name
    	<![if !IE]>
  • Error Line 60, Column 8: character data is not allowed here
    	<![if !IE]>

    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 62, Column 5: "endif" is not a reserved name
    	<![endif]>
  • Error Line 62, Column 10: character data is not allowed here
    	<![endif]>

    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 184, Column 30: required attribute "type" not specified
    <script language="javascript">var br_sitepath = "peteava"; var br_sitecode = "p…

    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 184, Column 197: there is no attribute "SRC"
    …br_sitepath; document.write("<IMG SRC=\""+IVW+"?r="+escape(document.referrer)+…

    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 184, Column 197: an attribute value must be a literal unless it contains only name characters
    …br_sitepath; document.write("<IMG SRC=\""+IVW+"?r="+escape(document.referrer)+…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 184, Column 313: there is no attribute "WIDTH"
    …een.width+"x"+screen.height+"\" WIDTH=\"1\" HEIGHT=\"1\" style=\"position: abs…

    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 184, Column 313: an attribute value must be a literal unless it contains only name characters
    …een.width+"x"+screen.height+"\" WIDTH=\"1\" HEIGHT=\"1\" style=\"position: abs…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 184, Column 326: there is no attribute "HEIGHT"
    …+screen.height+"\" WIDTH=\"1\" HEIGHT=\"1\" style=\"position: absolute;\">");<…

    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 184, Column 326: an attribute value must be a literal unless it contains only name characters
    …+screen.height+"\" WIDTH=\"1\" HEIGHT=\"1\" style=\"position: absolute;\">");<…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 184, Column 338: there is no attribute "style"
    ….height+"\" WIDTH=\"1\" HEIGHT=\"1\" style=\"position: absolute;\">");</SCRIPT>

    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 184, Column 338: an attribute value must be a literal unless it contains only name characters
    ….height+"\" WIDTH=\"1\" HEIGHT=\"1\" style=\"position: absolute;\">");</SCRIPT>

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 184, Column 358: "absolute" is not a member of a group specified for any attribute
    ….height+"\" WIDTH=\"1\" HEIGHT=\"1\" style=\"position: absolute;\">");</SCRIPT>
  • Error Line 184, Column 361: element "IMG" undefined
    ….height+"\" WIDTH=\"1\" HEIGHT=\"1\" style=\"position: absolute;\">");</SCRIPT>

    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).
  • Error Line 184, Column 373: end tag for element "SCRIPT" which is not open
    ….height+"\" WIDTH=\"1\" HEIGHT=\"1\" style=\"position: absolute;\">");</SCRIPT>

    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 224, Column 67: required attribute "alt" not specified
                        onclick="this.blur(); toggleUploadOptions(); ">

    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 224, Column 68: end tag for "area" omitted, but OMITTAG NO was specified
                        onclick="this.blur(); toggleUploadOptions(); ">

    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 221, Column 17: start tag was here
                    <area shape="poly" coords="1,0,37,30,74,30,36,0" href="javascri…
  • Error Line 234, Column 115: required attribute "alt" not specified
    …p="$('header_ptv_search_button').removeClass('click')" style="cursor:pointer;">

    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 234, Column 116: end tag for "area" omitted, but OMITTAG NO was specified
    …p="$('header_ptv_search_button').removeClass('click')" style="cursor:pointer;">

    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 232, Column 17: start tag was here
                	 		<area shape="poly" coords="0,30,37,30,0,0" id="upload_search_bu…
  • Error Line 237, Column 76: required attribute "alt" not specified
                                onclick="$('upload_btn_img').addClass('hover')">

    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 237, Column 77: end tag for "area" omitted, but OMITTAG NO was specified
                                onclick="$('upload_btn_img').addClass('hover')">

    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 236, Column 25: start tag was here
                            <area shape="poly" coords="1,0,37,30,121,30,85,0" href=…
  • Warning Line 240, Column 92: character "&" is the first character of a delimiter but occurred as data
    …"/upload" title="Incarca video si imagini">&nbsp;Video & Imagini&nbsp;</a></li>

    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.
  • Error Line 353, Column 117: document type does not allow element "link" here
    …ge/newhomepage.css" rel="stylesheet" /><script type="text/javascript" src="/tp…

    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 358, Column 14: ID "adoceanrotdefemdoff" already defined
        <div id="adoceanrotdefemdoff"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 338, Column 14: ID "adoceanrotdefemdoff" first defined here
        <div id="adoceanrotdefemdoff"></div>
  • Error Line 767, Column 14: ID "adoceanroqellhjnsea" already defined
        <div id="adoceanroqellhjnsea"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 525, Column 14: ID "adoceanroqellhjnsea" first defined here
        <div id="adoceanroqellhjnsea"></div>
  • Error Line 821, Column 14: ID "adoceanroqellhjnsea" already defined
        <div id="adoceanroqellhjnsea"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 525, Column 14: ID "adoceanroqellhjnsea" first defined here
        <div id="adoceanroqellhjnsea"></div>
  • Error Line 985, Column 14: ID "adoceanroqellhjnsea" already defined
        <div id="adoceanroqellhjnsea"></div>

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 525, Column 14: ID "adoceanroqellhjnsea" first defined here
        <div id="adoceanroqellhjnsea"></div>
  • Error Line 1098, Column 394: there is no attribute "allowTransparency"
    …verflow:hidden; width:1010px; height:185px;" allowTransparency="true"></iframe>

    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 1126, Column 29: reference not terminated by REFC delimiter
    				<span class="copy">&copy 2008-2013 peTeava.ro. Toate drepturile rezervate.<…

    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.

  • Error Line 1126, Column 88: document type does not allow element "h4" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …. Toate drepturile rezervate.<br /><h4><a href="http://www.peteava.ro/termeni"…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 1128, Column 184: duplicate specification of attribute "frameborder"
    …scrolling="no" marginheight="0" marginwidth="0" frameborder="0"></iframe></div>

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 1148, Column 7: end tag for "center" omitted, but OMITTAG NO was specified
    </body>

    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 191, Column 1: start tag was here
    <center>
  • Error Line 1148, Column 7: end tag for "IMG" omitted, but OMITTAG NO was specified
    </body>

    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 184, Column 188: start tag was here
    …cnt/CP/"+br_sitepath; document.write("<IMG SRC=\""+IVW+"?r="+escape(document.r…
  • Error Line 1148, Column 7: end tag for "script" omitted, but OMITTAG NO was specified
    </body>

    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 184, Column 1: start tag was here
    <script language="javascript">var br_sitepath = "peteava"; var br_sitecode = "p…
  • Error Line 1148, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 182, Column 1: start tag was here
    <div class="limiter">

Visitor Analysis

Daily Visitor
  • 3.500 visits
Daily Visitor