Onlinelinkscan is a fast, free antivirus tool that scans any suspicious websites for adware, trojans, viruses and malware. ...

onlinelinkscan.com
  • Domain Name
    onlinelinkscan.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #62210
  • Page Size
    23.8 KB
  • Ip Address
    69.16.192.73
  • Heading
    H1: 2, H2: 0, H3: 1, H4: 0, H5: 1, H6: 0
  • Images
    2 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Online Virus Scanner - Scan Links for Malware, Trojans and Viruses
  • Meta Keyword
    link scanner,url scanner,link scan,adware, malware, spyware, trojan, virus, worm,anti-virus, anti-virus URL scanner, link scanner , free anti-virus check, website free scanner
  • Meta Description
    Onlinelinkscan is a fast, free antivirus tool that scans any suspicious websites for adware, trojans, viruses and malware.

Technical Analysis

  • Webserver
    Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • Ip Address
    69.16.192.73
  • Domain Age
    4 Years, 2 Months, 6 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sat, 02 Mar 2013 07:27:48 GMT
  • server: Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
  • x-powered-by: PHP/5.4.10
  • x-pingback: http://onlinelinkscan.com/xmlrpc.php
  • connection: close
  • content-type: text/html; charset=UTF-8
  • content-length: 22478
  • age: 63
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for onlinelinkscan.com

IP 69.16.192.73 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Lansing
  • Continent Code
    48917
  • Latitude
    517
  • Longitude
    551
  • %rwhois V-1.5:003eff:00 rwhois.liquidweb.com (by Network Solutions, Inc. V-1.5.7.4)
    network:Class-Name:network
    network:ID:NETBLK-AVACTISHOSTI.69.16.192.73/32
    network:Auth-Area:69.16.192.0/18
    network:Network-Name:AVACTISHOSTI-69.16.192.73
    network:IP-Network:69.16.192.73/32
    network:IP-Network-Block:69.16.192.73-69.16.192.73
    network:Organization;I:AVACTISHOSTI
    network:Org-Name:avactishosting.com
    network:Street-Address:2224 Kirkbride Drive
    network:City:Danvers
    network:State:MA
    network:Postal-Code:01923
    network:Country-Code:US
    network:Tech-Contact;I:webaccounts@hbwsl.com
    network:Abuse:abuse@sourcedns.com
    network:Created:20130302
    network:Updated:20130302
    network:Updated-By:admin@sourcedns.com

    network:Class-Name:network
    network:ID:NETBLK-SOURCEDNS.69.16.192.0/18
    network:Auth-Area:69.16.192.0/18
    network:Network-Name:SOURCEDNS-69.16.192.0
    network:IP-Network:69.16.192.0/18
    network:IP-Network-Block:69.16.192.0 - 69.16.255.255
    network:Organization;I:SOURCEDNS
    network:Org-Name:SourceDNS
    network:Street-Address:4210 Creyts Rd.
    network:City:Lansing
    network:State:MI
    network:Postal-Code:48917
    network:Country-Code:US
    network:Tech-Contact;I:admin@sourcedns.com
    network:Created:20040212
    network:Updated:20060327
    network:Updated-By:admin@sourcedns.com
    network:Abuse:abuse@sourcedns.com

    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 52 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.6198866436668309
Message Error
  • Error Line 8, Column 57: document type does not allow element "html" here
    <html xmlns:fb="https://www.facebook.com/OnlineLinkScan">

    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 8, Column 1: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    <html xmlns:fb="https://www.facebook.com/OnlineLinkScan">

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 11, Column 127: document type does not allow element "link" here; assuming missing "head" start-tag
    …an.com/wp-content/themes/Aggregate/style.css" type="text/css" media="screen" />
  • Error Line 167, 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 236, Column 7: document type does not allow element "html" here
    	<html>

    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 236, Column 2: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    	<html>

    Many Document Types based on XML need a mandatory xmlns attribute on the root element. For example, the root element for XHTML might look like:
    <html xmlns="http://www.w3.org/1999/xhtml">

  • Error Line 238, Column 18: document type does not allow element "div" here
    <div id="fb-root"></div>

    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 239, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

    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 239, Column 8: document type does not allow element "script" here; assuming missing "head" start-tag
    <script>(function(d, s, id) {
  • Error Line 252, Column 47: document type does not allow element "div" here; assuming missing "object" start-tag
    …id="imagegif"  style ="display: none;"><center><img id="gifimage" src = "http:…
  • Error Line 252, Column 165: required attribute "alt" not specified
    …nkscan.com/wp-content/plugins/onlinelinkscan/images/loader.gif"></center></div>

    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 252, Column 174: end tag for "img" omitted, but OMITTAG NO was specified
    …nkscan.com/wp-content/plugins/onlinelinkscan/images/loader.gif"></center></div>

    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 252, Column 56: start tag was here
    …gif"  style ="display: none;"><center><img id="gifimage" src = "http://test.on…
  • Error Line 262, Column 41: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …    	  	<h1 ><p style="color:#000080;">Prevent infection and data theft with O…

    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 310, Column 93: there is no attribute "data-show-count"
    …witter-follow-button" data-show-count="true" data-show-screen-name="false">Fol…

    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 310, Column 122: there is no attribute "data-show-screen-name"
    …ata-show-count="true" data-show-screen-name="false">Follow @OnlineLinkScanS</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 311, Column 8: required attribute "type" not specified
    <script>!function(d,s,id){var js,fjs=d.getElementsByTagName(s)[0];if(!d.getElem…

    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 313, Column 44: there is no attribute "data-href"
    …       <div class="fb-like" data-href="https://www.facebook.com/OnlineLinkScan…

    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 313, Column 96: there is no attribute "data-send"
    …acebook.com/OnlineLinkScan" data-send="false" data-layout="button_count" data-…

    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 313, Column 116: there is no attribute "data-layout"
    …nkScan" data-send="false" data-layout="button_count" data-width="500" data-sho…

    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 313, Column 142: there is no attribute "data-width"
    …lse" data-layout="button_count" data-width="500" data-show-faces="false"></div>

    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 313, Column 164: there is no attribute "data-show-faces"
    …lse" data-layout="button_count" data-width="500" data-show-faces="false"></div>

    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 320, Column 57: there is no attribute "g:plusone:size"
    <a class="addthis_button_google_plusone" g:plusone:size="medium"></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 333, Column 7: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!----END Added By Priyanka On 20 dec 2012 -->
  • Info Line 333, Column 1: comment declaration started here
    <!----END Added By Priyanka On 20 dec 2012 -->
  • Error Line 335, Column 91: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …t face='Georgia' color='black'><center><table border='0' cellpadding='5'><tr><…

    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 335, Column 181: end tag for "strong" omitted, but OMITTAG NO was specified
    …strong>Statistics for Last 30 Days</td></strong></center></tr><font face='Geor…

    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 335, Column 142: start tag was here
    …r='0' cellpadding='5'><tr><td><center><strong>Statistics for Last 30 Days</td>…
  • Error Line 335, Column 181: end tag for "center" omitted, but OMITTAG NO was specified
    …strong>Statistics for Last 30 Days</td></strong></center></tr><font face='Geor…

    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 335, Column 134: start tag was here
    …le border='0' cellpadding='5'><tr><td><center><strong>Statistics for Last 30 D…
  • Error Line 335, Column 190: end tag for element "strong" which is not open
    …atistics for Last 30 Days</td></strong></center></tr><font face='Georgia'><tr>…

    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 335, Column 199: end tag for "tr" omitted, but OMITTAG NO was specified
    …for Last 30 Days</td></strong></center></tr><font face='Georgia'><tr><td><font…

    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 335, Column 126: start tag was here
    …ter><table border='0' cellpadding='5'><tr><td><center><strong>Statistics for L…
  • Error Line 335, Column 199: end tag for "table" omitted, but OMITTAG NO was specified
    …for Last 30 Days</td></strong></center></tr><font face='Georgia'><tr><td><font…

    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 335, Column 92: start tag was here
    … face='Georgia' color='black'><center><table border='0' cellpadding='5'><tr><t…
  • Error Line 335, Column 204: end tag for element "tr" which is not open
    …ast 30 Days</td></strong></center></tr><font face='Georgia'><tr><td><font colo…

    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 335, Column 229: document type does not allow element "tr" here
    …</center></tr><font face='Georgia'><tr><td><font color='black'>Links Scanned:-…

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

  • Warning Line 335, Column 280: reference not terminated by REFC delimiter
    …lor='black'>Links Scanned:-21,731&nbsp &nbsp<font color='green'>Clean:-15,975<…

    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.

  • Warning Line 335, Column 286: reference not terminated by REFC delimiter
    …lack'>Links Scanned:-21,731&nbsp &nbsp<font color='green'>Clean:-15,975</font>…

    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.

  • Warning Line 335, Column 349: reference not terminated by REFC delimiter
    …:-15,975</font><font color='red'>&nbsp &nbsp Suspicious:-5,756</font></tr></fo…

    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.

  • Warning Line 335, Column 355: reference not terminated by REFC delimiter
    …75</font><font color='red'>&nbsp &nbsp Suspicious:-5,756</font></tr></font></f…

    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 335, Column 384: end tag for "font" omitted, but OMITTAG NO was specified
    …bsp &nbsp Suspicious:-5,756</font></tr></font></font></h5><br></table></center…

    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 335, Column 234: start tag was here
    …ter></tr><font face='Georgia'><tr><td><font color='black'>Links Scanned:-21,73…
  • Error Line 335, Column 384: end tag for "td" omitted, but OMITTAG NO was specified
    …bsp &nbsp Suspicious:-5,756</font></tr></font></font></h5><br></table></center…

    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 335, Column 230: start tag was here
    …/center></tr><font face='Georgia'><tr><td><font color='black'>Links Scanned:-2…
  • Error Line 335, Column 415: end tag for element "table" which is not open
    …picious:-5,756</font></tr></font></font></h5><br></table></center></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 335, Column 415: end tag for "br" omitted, but OMITTAG NO was specified
    …picious:-5,756</font></tr></font></font></h5><br></table></center></font></div>

    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 335, Column 404: start tag was here
    …picious:-5,756</font></tr></font></font></h5><br></table></center></font></div>
  • Error Line 335, Column 424: end tag for element "center" which is not open
    …picious:-5,756</font></tr></font></font></h5><br></table></center></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 335, Column 431: end tag for element "font" which is not open
    …picious:-5,756</font></tr></font></font></h5><br></table></center></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.

  • Warning Line 338, Column 41: S separator in comment declaration
    <!-- -END Added By Priyanka 15 Nov2012-- -->

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Warning Line 351, Column 34: multiple comments in comment declaration
    <script type="text/javascript"><!--
  • Warning Line 351, Column 36: S separator in comment declaration
    <script type="text/javascript"><!--

    This may happen if you have consecutive comments but did not close one of them properly. The proper syntax for comments is <!-- my comment -->.

  • Error Line 352, Column 1: invalid comment declaration: found name start character outside comment but inside comment declaration
    google_ad_client = "ca-pub-8461867512759166";
  • Info Line 338, Column 1: comment declaration started here
    <!-- -END Added By Priyanka 15 Nov2012-- -->
  • Error Line 358, Column 9: end tag for element "script" which is not open
    </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 363, Column 9: end tag for element "center" which is not open
    </center>

    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 364, Column 56: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …Priyanka 20 dec 2012--><center><p><h3 ><div class="signup"><a href="http://onl…

    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 364, Column 76: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …--><center><p><h3 ><div class="signup"><a href="http://onlinelinkscan.com/memb…

    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 369, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    	</div>

    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 252, Column 4: start tag was here
       <div id="imagegif"  style ="display: none;"><center><img id="gifimage" src =…
  • Error Line 369, Column 7: "head" not finished but containing element ended
    	</div>
  • Error Line 369, Column 7: end tag for "head" omitted, but OMITTAG NO was specified
    	</div>

    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 239, Column 1: start tag was here
    <script>(function(d, s, id) {
  • Error Line 369, Column 7: "html" not finished but containing element ended
    	</div>
  • Error Line 369, Column 7: end tag for "html" omitted, but OMITTAG NO was specified
    	</div>

    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 2: start tag was here
    	<html>
  • Error Line 379, Column 5: invalid comment declaration: found name start character outside comment but inside comment declaration
    <!--END COMMENTED OUT BY SHILPA ON 15-NOV-2012		-->
  • Info Line 370, Column 1: comment declaration started here
    <!--BEGIN COMMENTED OUT BY SHILPA ON 15-NOV-2012
  • Error Line 403, Column 7: end tag for element "div" which is not open
    	</div> <!-- end #content-area -->

    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 435, Column 8: end tag for "head" omitted, but OMITTAG NO was specified
    </html>

    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 4, Column 1: start tag was here
    <head profile="http://gmpg.org/xfn/11">
  • Error Line 435, Column 8: "html" not finished but document ended
    </html>
  • Error Line 435, Column 8: end tag for "html" omitted, but OMITTAG NO was specified
    </html>

    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 3, Column 1: start tag was here
    <html xmlns="http://www.w3.org/1999/xhtml" lang="en-US">

Visitor Analysis

Daily Visitor
  • 2.217 visits
Daily Visitor