Akiba-Online ...

akiba-online.com
  • Domain Name
    akiba-online.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #2306
  • Page Size
    33.3 KB
  • Ip Address
    76.73.47.19
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    3 GIF, 1 JPG, 0 PNG

Website Meta Analysis

  • Title
    Akiba-Online
  • Meta Keyword
    akiba,jav,av,hentai,jr idols,idol,idols,IV,junior,japan,hentai,torrents,torrent,manga,anime,games,U-15,saaya,download,rapidshare,megaupload,ddl,u15,akihabara,hotfile,direct,download
  • Meta Description
    Akiba-Online

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    76.73.47.19
  • Domain Age
    6 Years, 9 Months, 21 days.
  • Javascript Library
    yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from akiba-online.com.

HTML Analysis

  • content-type: text/html; charset=ISO-8859-1
  • cache-control: private
  • pragma: private
  • x-ua-compatible: IE=7
  • x-geoip:
  • vary: Accept-Encoding
  • content-length: 31194
  • date: Sat, 17 Aug 2013 07:01:55 GMT
  • x-varnish: 1593255499 1593216210
  • age: 820
  • connection: keep-alive
  • server: nginx
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: akiba-online.com

Registrant:
chompy chan c/o Dynadot Privacy
PO Box 701
San Mateo, CA 94401
United States

Administrative Contact:
chompy chan c/o Dynadot Privacy
PO Box 701
San Mateo, CA 94401
United States
email
1-650-585-4708

Technical Contact:
chompy chan c/o Dynadot Privacy
PO Box 701
San Mateo, CA 94401
United States
email
1-650-585-4708

Record expires on 2013/10/31 UTC
Record created on 2006/10/31 UTC

Domain servers in listed order:
ns1.dynadot.com
ns2.dynadot.com

DNS Analysis


DNS servers
ns2.dynadot.com [50.112.108.69]
ns1.dynadot.com [50.112.107.96]

DNS Records

Answer records
akiba-online.com SOA
server: ns1.dynadot.com
email: hostmaster@akiba-online.com
serial: 1356128084
refresh: 16384
retry: 2048
expire: 1048576
minimum ttl: 2560
2560s
akiba-online.com NS  ns1.dynadot.com 1800s
akiba-online.com NS  ns2.dynadot.com 1800s
akiba-online.com MX
preference: 0
exchange: aspmx.l.google.com
1800s
akiba-online.com MX
preference: 1
exchange: alt1.aspmx.l.google.com
1800s
akiba-online.com MX
preference: 1
exchange: alt2.aspmx.l.google.com
1800s
akiba-online.com TXT v=spf1 a mx ~all 1800s
akiba-online.com A 76.73.47.19 1800s

Authority records

Additional records
ns1.dynadot.com A 50.112.114.198 14400s
ns1.dynadot.com A 50.112.107.96 14400s
ns2.dynadot.com A 50.112.108.69 14400s

IP 76.73.47.19 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Chicago
  • Continent Code
    60604
  • Latitude
    312
  • Longitude
    602
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 76.73.47.19"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=76.73.47.19?showDetails=true&showARIN=false&ext=netref2
    #

    FDCservers.net FDCSERVERS (NET-76-73-0-0-1) 76.73.0.0 - 76.73.127.255
    FDCservers.net FDCSERVERS-DENVER (NET-76-73-0-0-2) 76.73.0.0 - 76.73.127.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 8 Errors
  • 0 Warnings
Ratio Text/Html
  • 0.741783211657431
Message Error
  • Error Line 110, Column 13: end tag for "table" omitted, but OMITTAG NO was specified
            </tr>

    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 105, Column 7: start tag was here
          <table width="100%" border="0" cellpadding="0" cellspacing="0">
  • Error Line 110, Column 13: end tag for "td" omitted, but OMITTAG NO was specified
            </tr>

    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 104, Column 5: start tag was here
        <td width="100%" class="logo_bg" style="background-image: url(images/bluefa…
  • Error Line 139, Column 5: end tag for element "td" which is not open
    </td></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 139, Column 10: end tag for element "tr" which is not open
    </td></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 141, Column 8: end tag for element "table" which is not open
    </table>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 156, Column 108: required attribute "alt" not specified
    …line.com/forum/images/ryuban.gif" border="2" style="border:2px solid black;" />

    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 268, Column 23: document type does not allow element "style" here
    <style type="text/css">.nfjselected {font-weight: bold;} .nfjlink {font-size: 1…

    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 489, Column 112: required attribute "alt" not specified
    …l=a57445938714"><img src="http://www.akiba-online.com/forum/images/bs.gif"></a>

    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 489, Column 116: end tag for "img" omitted, but OMITTAG NO was specified
    …l=a57445938714"><img src="http://www.akiba-online.com/forum/images/bs.gif"></a>

    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 489, Column 54: start tag was here
    …/bitshare.com/?referral=a57445938714"><img src="http://www.akiba-online.com/fo…
  • Error Line 491, Column 92: "tr" not finished but containing element ended
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></tr>
  • Error Line 491, Column 92: end tag for "tr" omitted, but OMITTAG NO was specified
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></tr>

    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 491, Column 12: start tag was here
    </td></tr> <tr onmouseover="this.className='alt1'" onmouseout="this.className='…
  • Error Line 491, Column 92: end tag for "table" omitted, but OMITTAG NO was specified
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></tr>

    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 487, Column 28: start tag was here
    				<tr> <td class="alt2"> <table border="0" cellpadding="0" cellspacing="0" wi…
  • Error Line 491, Column 106: end tag for "tbody" omitted, but OMITTAG NO was specified
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></tr>

    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 485, Column 3: start tag was here
    		<tbody id="collapseobj_module_29" style="">
  • Error Line 491, Column 111: end tag for "div" omitted, but OMITTAG NO was specified
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></tr>

    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 474, Column 1: start tag was here
    <div style="padding-bottom:15px">
  • Error Line 491, Column 111: end tag for "td" omitted, but OMITTAG NO was specified
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></tr>

    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 405, Column 4: start tag was here
    			<td width="175" style="padding-right: 15px">
  • Error Line 493, Column 10: end tag for element "tbody" which is not open
    		</tbody>

    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 522, Column 8: end tag for element "td" which is not open
    			</td>

    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 525, Column 20: document type does not allow element "td" here
    			<td valign="top">

    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 558, Column 118: there is no attribute "onload"
    …0&amp;h=552" border="0" alt="" onload="NcodeImageResizer.createOn(this);" /><b…

    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 567, Column 314: there is no attribute "src"
    …ss" value="always"></param><embed src="http://www.youtube.com/v/7_D4nsrec7Q&am…

    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 567, Column 448: there is no attribute "type"
    …eature=player_embedded&amp;fs=1" type="application/x-shockwave-flash" allowful…

    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 567, Column 496: there is no attribute "allowfullscreen"
    …on/x-shockwave-flash" allowfullscreen="true" allowScriptAccess="always" width=…

    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 567, Column 521: there is no attribute "allowScriptAccess"
    …owfullscreen="true" allowScriptAccess="always" width="640" height="385"></embe…

    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 567, Column 536: there is no attribute "width"
    …rue" allowScriptAccess="always" width="640" height="385"></embed></object><br …

    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 567, Column 549: there is no attribute "height"
    …ue" allowScriptAccess="always" width="640" height="385"></embed></object><br />

    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 567, Column 554: element "embed" undefined
    …ue" allowScriptAccess="always" width="640" height="385"></embed></object><br />

    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 873, Column 59: document type does not allow element "td" here
    			<td valign="top" width="175" style="padding-left: 15px">

    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 891, Column 13: there is no attribute "SRC"
    <IFRAME SRC="http://www.ppc-direct.com/index10.html?affid=121010" width="150" h…

    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 891, Column 73: there is no attribute "width"
    ….com/index10.html?affid=121010" width="150" height="500" frameborder="no" scro…

    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 891, Column 86: there is no attribute "height"
    …html?affid=121010" width="150" height="500" frameborder="no" scrolling="no"></…

    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 891, Column 104: there is no attribute "frameborder"
    …fid=121010" width="150" height="500" frameborder="no" scrolling="no"></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.

  • Error Line 891, Column 119: there is no attribute "scrolling"
    …fid=121010" width="150" height="500" frameborder="no" scrolling="no"></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.

  • Error Line 891, Column 123: element "IFRAME" undefined
    …fid=121010" width="150" height="500" frameborder="no" scrolling="no"></IFRAME> 

    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 893, Column 92: "tr" not finished but containing element ended
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></tr>
  • Error Line 893, Column 92: end tag for "tr" omitted, but OMITTAG NO was specified
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></tr>

    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 893, Column 12: start tag was here
    </td></tr> <tr onmouseover="this.className='alt1'" onmouseout="this.className='…
  • Error Line 893, Column 92: end tag for "table" omitted, but OMITTAG NO was specified
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></tr>

    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 889, Column 28: start tag was here
    				<tr> <td class="alt2"> <table border="0" cellpadding="0" cellspacing="0" wi…
  • Error Line 893, Column 106: end tag for "tbody" omitted, but OMITTAG NO was specified
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></tr>

    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 887, Column 3: start tag was here
    		<tbody id="collapseobj_module_28" style="">
  • Error Line 893, Column 111: end tag for element "tr" which is not open
    ….className='alt1'" onmouseout="this.className='alt2'"> </td></tr> </table></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 895, Column 10: end tag for element "tbody" which is not open
    		</tbody>

    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 896, Column 9: end tag for element "table" which is not open
    	</table>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1253, Column 6: end tag for element "tr" which is not open
    	</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 1254, Column 8: end tag for element "table" which is not open
    </table>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1327, Column 6: end tag for element "div" which is not open
    </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
  • 22.167 visits