Hosting Bulk - Dedicated Hosting Service ...

hostingbulk.com
  • Domain Name
    hostingbulk.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #24606
  • Page Size
    11.8 KB
  • Ip Address
    91.236.116.31
  • Heading
    H1: 4, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Hosting Bulk - Dedicated Host
  • Meta Keyword
    web hosting, dedicated server, email hosting, enterprise, webhosting, hosting, spam server
  • Meta Description
    Hosting Bulk - Dedicated Hosting Service

Technical Analysis

  • Webserver
    nginx/1.4.1
  • Ip Address
    91.236.116.31
  • Domain Age
    6 Years, 11 Months, 26 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.4.1
  • date: Sat, 29 Jun 2013 01:08:23 GMT
  • content-type: text/html; charset=UTF-8
  • content-length: 3335
  • connection: keep-alive
  • expires: Fri, 28 Jun 2013 01:24:42 GMT
  • vary: Accept-Encoding
  • content-encoding: gzip
  • cache-control: public
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain name: hostingbulk.com

Registrant Contact:
WhoisGuard
WhoisGuard Protected ()

Fax:
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Administrative Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Technical Contact:
WhoisGuard
WhoisGuard Protected ( email )
+1.6613102107
Fax: +1.6613102107
11400 W. Olympic Blvd. Suite 200
Los Angeles, CA 90064
US

Status: Locked

Name Servers:
NS1.HOSTINGBULK.COM
NS2.HOSTINGBULK.COM

Creation date: 09 Jul 2006 09:41:00
Expiration date: 09 Jul 2013 09:41:00

IP 91.236.116.31 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 49 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.6683258669321387
Message Error
  • Error Line 40, Column 20: required attribute "action" not specified
    <form method="post">

    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 95, Column 64: required attribute "action" not specified
    <form method="post" onsubmit="return CheckForm(this)" name="NU">

    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 174, Column 36: 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 174, Column 53: 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 192, Column 52: there is no attribute "onClick"
    …radio" name="ut" value="file" onClick="changeUploadType('file')" id="r_file" c…

    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 192, Column 98: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …ploadType('file')" id="r_file" checked><label for="r_file">File upload</label>…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 192, Column 99: end tag for "input" omitted, but OMITTAG NO was specified
    …loadType('file')" id="r_file" checked><label for="r_file">File upload</label> …

    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 192, Column 1: start tag was here
    <input type="radio" name="ut" value="file" onClick="changeUploadType('file')" i…
  • Error Line 194, Column 88: end tag for "input" omitted, but OMITTAG NO was specified
    …="changeUploadType('url')" id="r_url"><label for="r_url">Remote URL upload</la…

    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 194, Column 1: start tag was here
    <input type="radio" name="ut" value="url" onClick="changeUploadType('url')" id=…
  • Error Line 200, Column 140: there is no attribute "onSubmit"
    …/fs8/upload.cgi?upload_id=" method="post" onSubmit="return StartUpload(this);">

    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 201, Column 54: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="upload_type" value="file">

    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 201, Column 1: start tag was here
    <input type="hidden" name="upload_type" value="file">
  • Error Line 202, Column 46: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="sess_id" value="">

    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 202, Column 1: start tag was here
    <input type="hidden" name="sess_id" value="">
  • Error Line 203, Column 74: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="srv_tmp_url" value="http://208.53.158.40/tmp">

    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 203, Column 1: start tag was here
    <input type="hidden" name="srv_tmp_url" value="http://208.53.158.40/tmp">
  • Error Line 204, Column 20: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table cellpadding=0 cellspacing=0 id="div_uf1" class="div1" style="position:st…
  • Error Line 204, Column 34: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <table cellpadding=0 cellspacing=0 id="div_uf1" class="div1" style="position:st…
  • Error Line 204, Column 102: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …pacing=0 id="div_uf1" class="div1" style="position:static;"><tr><td valign=top>
  • Error Line 205, Column 37: end tag for "br" omitted, but OMITTAG NO was specified
    <b>Up to 500 Mb, 1 files max</b><br>

    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 205, Column 33: start tag was here
    <b>Up to 500 Mb, 1 files max</b><br>
  • Error Line 206, Column 96: end tag for "input" omitted, but OMITTAG NO was specified
    …d_input"><input id="my_file_element" type="file" name="file_1" size="50"></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 206, Column 27: start tag was here
    <div class="upload_input"><input id="my_file_element" type="file" name="file_1"…
  • Error Line 209, Column 47: there is no attribute "onClick"
    …"#" style="line-height:20px;" onClick="$$('optidiv').style.position='static';t…

    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 211, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …input type="text" name="link_rcpt" class="myForm" size=24 maxlength=42> &nbsp; 
  • Error Line 211, Column 89: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …input type="text" name="link_rcpt" class="myForm" size=24 maxlength=42> &nbsp; 
  • Error Line 211, Column 92: end tag for "input" omitted, but OMITTAG NO was specified
    …input type="text" name="link_rcpt" class="myForm" size=24 maxlength=42> &nbsp; 

    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 211, Column 20: start tag was here
    Recipient's Email: <input type="text" name="link_rcpt" class="myForm" size=24 m…
  • Error Line 212, Column 72: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    Link Password: <input type="text" name="link_pass" class="myForm" size=8>
  • Error Line 212, Column 74: end tag for "input" omitted, but OMITTAG NO was specified
    Link Password: <input type="text" name="link_pass" class="myForm" size=8>

    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 212, Column 16: start tag was here
    Link Password: <input type="text" name="link_pass" class="myForm" size=8>
  • Error Line 214, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 214, Column 1: start tag was here
    <br>
  • Error Line 216, Column 130: ID "tos" already defined
    …e="checkbox" name="tos" value="1" id="tos" checked onClick="if(this.checked){t…

    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 161, Column 17: ID "tos" first defined here
            <li id="tos"><a href="http://hostingbulk.com/tos.html">Terms of service…
  • Error Line 216, Column 143: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …name="tos" value="1" id="tos" checked onClick="if(this.checked){this.form.subm…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 216, Column 260: end tag for "input" omitted, but OMITTAG NO was specified
    …_btn.disabled=false}else{this.form.submit_btn.disabled=true};this.blur();"><br>

    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 216, Column 82: start tag was here
    …he</label> <a href="tos.html">TOS</a> <input type="checkbox" name="tos" value=…
  • Error Line 216, Column 264: end tag for "br" omitted, but OMITTAG NO was specified
    …_btn.disabled=false}else{this.form.submit_btn.disabled=true};this.blur();"><br>

    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 216, Column 260: start tag was here
    …_btn.disabled=false}else{this.form.submit_btn.disabled=true};this.blur();"><br>
  • Error Line 217, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="submit" name="submit_btn" value=" Upload! " class="btn">

    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 217, Column 1: start tag was here
    <input type="submit" name="submit_btn" value=" Upload! " class="btn">
  • Error Line 219, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 219, Column 1: start tag was here
    <br>
  • Error Line 229, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br><b><a href="?op=registration">Register on site</a><br>to use Remote…

    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 229, Column 1: start tag was here
    <br><br><br><b><a href="?op=registration">Register on site</a><br>to use Remote…
  • Error Line 229, Column 9: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br><b><a href="?op=registration">Register on site</a><br>to use Remote…

    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 229, Column 5: start tag was here
    <br><br><br><b><a href="?op=registration">Register on site</a><br>to use Remote…
  • Error Line 229, Column 13: end tag for "br" omitted, but OMITTAG NO was specified
    <br><br><br><b><a href="?op=registration">Register on site</a><br>to use Remote…

    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 229, Column 9: start tag was here
    <br><br><br><b><a href="?op=registration">Register on site</a><br>to use Remote…
  • Error Line 229, Column 67: end tag for "br" omitted, but OMITTAG NO was specified
    …<a href="?op=registration">Register on site</a><br>to use Remote URL upload</b>

    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 229, Column 63: start tag was here
    …<a href="?op=registration">Register on site</a><br>to use Remote URL upload</b>
  • Error Line 247, Column 73: there is no attribute "SCROLLING"
    …ess_frame" name="transfer2" SCROLLING=NO frameborder=0 style="width: 395px; he…

    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 247, Column 73: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ess_frame" name="transfer2" SCROLLING=NO frameborder=0 style="width: 395px; he…
  • Error Line 247, Column 88: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …="transfer2" SCROLLING=NO frameborder=0 style="width: 395px; height: 200px;"><…
  • Error Line 257, Column 31: 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 272, Column 33: there is no attribute "FRAMEBORDER"
    		  					 		<IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WID…

    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 272, Column 33: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    		  					 		<IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WID…
  • Error Line 272, Column 47: there is no attribute "MARGINWIDTH"
    …	 		<IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …

    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 272, Column 47: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …	 		<IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 …
  • Error Line 272, Column 62: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…

    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 272, Column 62: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC=…
  • Error Line 272, Column 74: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.…

    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 272, Column 74: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.…
  • Error Line 272, Column 83: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.tlvmedia.…

    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 272, Column 83: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.tlvmedia.…
  • Error Line 272, Column 94: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.tlvmedia.com/?id=101…

    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 272, Column 94: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …EIGHT=0 SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.tlvmedia.com/?id=101…
  • Error Line 272, Column 102: there is no attribute "SRC"
    …SCROLLING=NO WIDTH=300 HEIGHT=250 SRC="http://tag.tlvmedia.com/?id=101815_1249…

    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 272, Column 145: cannot generate system identifier for general entity "ad_type"
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 272, Column 145: general entity "ad_type" not defined and no default entity
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 272, Column 152: reference not terminated by REFC delimiter
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME>

    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 272, Column 152: reference to external entity in attribute value
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 272, Column 152: reference to entity "ad_type" for which no system identifier could be generated
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 272, Column 144: entity was defined here
    …p://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAM…
  • Warning Line 272, Column 160: cannot generate system identifier for general entity "ad_size"
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME>

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 272, Column 160: general entity "ad_size" not defined and no default entity
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 272, Column 167: reference not terminated by REFC delimiter
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME>

    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 272, Column 167: reference to external entity in attribute value
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME>

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 272, Column 167: reference to entity "ad_size" for which no system identifier could be generated
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME>

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 272, Column 159: entity was defined here
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></IFRAME>
  • Error Line 272, Column 176: element "IFRAME" undefined
    …://tag.tlvmedia.com/?id=101815_124942&ad_type=banner&ad_size=300x250"></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 276, Column 62: there is no attribute "SRC"
    …com < - DO NOT MODIFY --> <SCRIPT SRC="http://ads.cpxinteractive.com/ttj?id=93…

    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 276, Column 107: cannot generate system identifier for general entity "size"
    …IFY --> <SCRIPT SRC="http://ads.cpxinteractive.com/ttj?id=938052&size=300x250" 

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 276, Column 107: general entity "size" not defined and no default entity
    …IFY --> <SCRIPT SRC="http://ads.cpxinteractive.com/ttj?id=938052&size=300x250" 

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 276, Column 111: reference not terminated by REFC delimiter
    …IFY --> <SCRIPT SRC="http://ads.cpxinteractive.com/ttj?id=938052&size=300x250" 

    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 276, Column 111: reference to external entity in attribute value
    …IFY --> <SCRIPT SRC="http://ads.cpxinteractive.com/ttj?id=938052&size=300x250" 

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 276, Column 111: reference to entity "size" for which no system identifier could be generated
    …IFY --> <SCRIPT SRC="http://ads.cpxinteractive.com/ttj?id=938052&size=300x250" 

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 276, Column 106: entity was defined here
    …IFY --> <SCRIPT SRC="http://ads.cpxinteractive.com/ttj?id=938052&size=300x250" 
  • Error Line 277, Column 6: there is no attribute "TYPE"
    TYPE="text/javascript"></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 277, Column 23: element "SCRIPT" undefined
    TYPE="text/javascript"></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 337, Column 7: end tag for element "BODY" which is not open
    </BODY>

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

    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 338, Column 8: end tag for "body" 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 29, Column 1: start tag was here
    <body>
  • Error Line 338, 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" xml:lang="en" lang="en">

Visitor Analysis

Daily Visitor
  • 9.567 visits