Click To Bookmark Us Search File : Latest Updates Welcome to the all new updated Zwaper.com More Updates... Select Categories Android Zone [5103] Animations [3350] Flash Files [45] Full Movies [17] Fun Stuff ...

zwaper.com
  • Domain Name
    zwaper.com
  • Favicon
  • Google Page Rank
    1
  • Alexa Rank
    #1046955
  • Page Size
    7.3 KB
  • Ip Address
    198.1.107.162
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    25 GIF, 0 JPG, 3 PNG

Website Meta Analysis

  • Title
    Zwaper.com- One Stop Mobile Downloads Portal.
  • Meta Keyword
  • Meta Description
    Click To Bookmark Us Search File : Latest Updates Welcome to the all new updated Zwaper.com More Updates... Select Categories Android Zone [5103] Animations [3350] Flash Files [45] Full Movies [17] Fun Stuff [34] Games [8938] Music [246] PC ...

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    198.1.107.162
  • Domain Age
    2 Years, 5 Months, 20 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 29 Jun 2013 15:54:21 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.17
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 1809
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registration Service Provided By: BIGROCK

Domain Name: ZWAPER.COM

Registration Date: 21-Jan-2011
Expiration Date: 21-Jan-2014

Status:LOCKED

DNS Analysis


DNS servers
ns1.zwaper.com [198.1.115.15]
ns2.zwaper.com [198.1.115.12]


DNS Records

Answer records
zwaper.com TXT v=spf1 +a +mx +ip4:198.1.107.162 ?all 14400s
zwaper.com MX
preference: 0
exchange: zwaper.com
14400s
zwaper.com SOA
server: ns1.zwaper.com
email: koolwap@gmail.com
serial: 2013020500
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
zwaper.com NS  ns2.zwaper.com 86400s
zwaper.com NS  ns1.zwaper.com 86400s
zwaper.com A 198.1.107.162 14400s

Authority records

Additional records
zwaper.com A 198.1.107.162 14400s
ns1.zwaper.com A 198.1.115.15 14400s
ns2.zwaper.com A 198.1.115.12 14400s

IP 198.1.107.162 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • %rwhois V-1.5:000080:00 rwhois.unifiedlayer.com (by Unified Layer, V-1.0.0)
    network:Class-Name:network
    network:ID: NETBLK-UL.198.1.107.162/32
    network:Auth-Area: 198.1.107.162/32
    network:Network-Name: UL-198.1.107.162/32
    network:IP-Network: 198.1.107.162/32
    network:Organization: websitewelcome.com
    network:Tech-Contact: abuse@websitewelcome.com
    network:Admin-Contact: abuse@websitewelcome.com
    network:Abuse-Contact: abuse@websitewelcome.com
    network:Created: 20130103
    network:Updated: 20130103
    network:Updated-By: abuse@websitewelcome.com

    %ok

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.7146292585170341
Message Error
  • Error Line 11, Column 45: there is no attribute "align"
                        <div class="logo" align="center">

    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 16, Column 38: there is no attribute "type"
                            <script type="text/javascript">

    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 16, Column 55: element "script" undefined
                            <script type="text/javascript">

    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 28, Column 13: there is no attribute "src"
    <script src="http://scripts.chitika.net/eminimalls/amm.js" type="text/javascrip…

    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 82: element "script" undefined
    …ript src="http://scripts.chitika.net/eminimalls/amm.js" type="text/javascript">

    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 30, Column 33: element "script" undefined
      <script type="text/javascript">

    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 54, Column 91: value of attribute "method" cannot be "POST"; must be one of "get", "post"
    …="http://zwaper.com/category/search.html" method="POST" accept-charset="utf-8">

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 54, Column 108: there is no attribute "accept-charset"
    …="http://zwaper.com/category/search.html" method="POST" accept-charset="utf-8">

    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 55, Column 72: document type does not allow element "input" here; missing one of "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
                                <input type="text" name="search" value="" />

    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 56, Column 66: document type does not allow element "input" here; missing one of "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
                                <input type="submit" value="Search" />

    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 57, Column 31: end tag for "form" which is not finished
                            </form>

    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 99, Column 54: element "script" undefined
                           <script type="text/javascript">

    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 111, Column 82: element "script" undefined
    …ript src="http://scripts.chitika.net/eminimalls/amm.js" type="text/javascript">

    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 117, Column 79: there is no attribute "alt"
    …href="http://zwaper.com/category/topFiles.html" alt="topfiles">Top 21 Files</a>

    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 134, Column 78: element "script" undefined
    …                <script type="text/javascript" src="onlyPopupOnce.js"></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).

Visitor Analysis

Daily Visitor
  • 187 visits