ariskar.ir

آگهی استخدام اریسکار | اگهی استخدام |سایت استخدام|استخدامی ...

Display Widget for this domain on your website. Click Here
This data was last updated from 19-09-2013 04:43:38  (update).

Overview Info

  • Domain Name
    ariskar.ir
  • Favicon
  • Alexa Rank
    #27157
  • Google Page Rank
    PR 1
  • Ip Address
    5.61.25.91
  • Page Size
    61 KB
  • Images
    8 GIF, 0 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    7 13 13 0 0 0

Website Meta Analysis



  • Title
    آگهی استخدام اریسکار
  • Meta Keyword
    آگهی استخدام اریسکار | اگهی استخدام |سایت استخدام|استخدامی,آگهی استخدام اریسکار,http://www.bsi.ir/PortalData/Subsystems/StaticContent/uploads/Image/fa/File/estekhdam.pdf,www.bsi.ir,استخدام بانک صادرات,استخدام بانک صادرات92,استخدام جدید بانک صادرات,استخدام جدید بانک صادرات1392,استخدام جدید صادرات,استخدامی بانک صادرات,استخدامی جدید بانک صادرات
  • Meta Description
    آگهی استخدام اریسکار | اگهی استخدام |سایت استخدام|استخدامی

Technical Analysis



  • Webserver
    Apache/2
  • Ip Address
    5.61.25.91
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from ariskar.ir.

HTML Analysis

  • date: Thu, 19 Sep 2013 04:41:46 GMT
  • server: Apache/2
  • x-powered-by: PHP/5.3.21
  • x-pingback: http://ariskar.ir/xmlrpc.php
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 11085
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
% This is the IRNIC Whois server v1.6.2.
% Available on web at http://whois.nic.ir/
% Find the terms and conditions of use on http://www.nic.ir/
%
% This server uses UTF-8 as the encoding for requests and responses.

% NOTE: This output has been filtered.

% Information related to 'ariskar.ir'


domain: ariskar.ir
ascii: ariskar.ir
remarks: (Domain Holder) mohsen sabahy bady
remarks: (Domain Holder Address) arisman, nanatz, esfehan, IR
holder-c: ms3681-irnic
admin-c: fa482-irnic
tech-c: fa482-irnic
bill-c: fa482-irnic
nserver: ns1.arisfa.ir
nserver: ns2.arisfa.ir
last-updated: 2012-09-26
expire-date: 2013-01-20
source: IRNIC # Filtered

nic-hdl: ms3681-irnic
person: mohsen sabahy bady
e-mail: email
address: arisman, nanatz, esfehan, IR
phone: 03624393900
source: IRNIC # Filtered

nic-hdl: fa482-irnic
org: Faraso Samaneh Pasargad Co.
e-mail: email
address: Unit 16, No. 73, Taherian St., Taleghani Crossroad, Shariati St.,, Tehran, Tehran, IR
phone: +98 21 7762 4118
fax-no: +98 21 7762 4116
source: IRNIC # Filtered

IP 5.61.25.91 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 290 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.7465674507921267
Message Error
  • Error Line 1, Column 1: no document type declaration; will parse without validation
    <head>

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Error Line 5, Column 3: "DOCTYPE" declaration not allowed in instance
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.o…
  • Warning Line 8, Column 68: NET-enabling start-tag requires SHORTTAG YES
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 9, Column 114: NET-enabling start-tag requires SHORTTAG YES
    …استخدام اریسکار - اگهی استخدام |سایت استخدام|استخدامی,آگهی استخدام اریسکار " />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 10, Column 95: NET-enabling start-tag requires SHORTTAG YES
    …iption" content="آگهی استخدام اریسکار | اگهی استخدام |سایت استخدام|استخدامی" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 16, Column 112: NET-enabling start-tag requires SHORTTAG YES
    …//ariskar.ir/wp-content/themes/kar/style.css" type="text/css" media="screen" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 17, Column 124: NET-enabling start-tag requires SHORTTAG YES
    …l" title="آگهی استخدام اریسکار RSS Feed" href="http://ariskar.ir/?feed=rss2" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 18, Column 58: NET-enabling start-tag requires SHORTTAG YES
    <link rel="pingback" href="http://ariskar.ir/xmlrpc.php" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 20, Column 156: NET-enabling start-tag requires SHORTTAG YES
    …t/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70' type='text/css' media='all' />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 21, Column 100: NET-enabling start-tag requires SHORTTAG YES
    …pe="application/rsd+xml" title="RSD" href="http://ariskar.ir/xmlrpc.php?rsd" />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 22, Column 113: NET-enabling start-tag requires SHORTTAG YES
    …ation/wlwmanifest+xml" href="http://ariskar.ir/wp-includes/wlwmanifest.xml" /> 

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 57, Column 77: NET-enabling start-tag requires SHORTTAG YES
    … face="Tahoma"><input type="text" style="width:140px" name="email"/></font></p>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 58, Column 75: NET-enabling start-tag requires SHORTTAG YES
    …idden" value="ariskar/HpPv" name="uri"/><input type="hidden" name="loc" value=…

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 58, Column 122: NET-enabling start-tag requires SHORTTAG YES
    …alue="ariskar/HpPv" name="uri"/><input type="hidden" name="loc" value="en_US"/>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 60, Column 55: NET-enabling start-tag requires SHORTTAG YES
    		<input type="submit" value="عضو&#1740;ت در خبرنامه" /></font><p>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 309, Column 162: end tag for element "SCRIPT" which is not open
    ….histats.com/js15.js%27 type=%27text/javascript%27%3E%3C/script%3E"));</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.

  • Warning Line 318, Column 102: cannot generate system identifier for general entity "amp"
    …ript" src="http://www.webgozar.ir/c.aspx?Code=1829739&amp;t=counter" ></script>

    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 318, Column 102: general entity "amp" not defined and no default entity
    …ript" src="http://www.webgozar.ir/c.aspx?Code=1829739&amp;t=counter" ></script>

    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.

  • Error Line 318, Column 105: reference to entity "amp" for which no system identifier could be generated
    …ript" src="http://www.webgozar.ir/c.aspx?Code=1829739&amp;t=counter" ></script>

    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 318, Column 101: entity was defined here
    …ript" src="http://www.webgozar.ir/c.aspx?Code=1829739&amp;t=counter" ></script>
  • Error Line 322, Column 5: end tag for element "UL" which is not open
    </ul>

    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 327, 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.

  • Error Line 348, 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 349, 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.

  • Error Line 350, 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.

  • Warning Line 353, Column 73: cannot generate system identifier for general entity "u"
    …" src="http://www.ad2ad.ir/showad.aspx?s=8&u=634914641388315473&p=tl"></script>

    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 353, Column 73: general entity "u" not defined and no default entity
    …" src="http://www.ad2ad.ir/showad.aspx?s=8&u=634914641388315473&p=tl"></script>

    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.

  • Error Line 353, Column 74: reference to entity "u" for which no system identifier could be generated
    …" src="http://www.ad2ad.ir/showad.aspx?s=8&u=634914641388315473&p=tl"></script>

    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 353, Column 72: entity was defined here
    …" src="http://www.ad2ad.ir/showad.aspx?s=8&u=634914641388315473&p=tl"></script>
  • Warning Line 353, Column 94: cannot generate system identifier for general entity "p"
    …" src="http://www.ad2ad.ir/showad.aspx?s=8&u=634914641388315473&p=tl"></script>

    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 353, Column 94: general entity "p" not defined and no default entity
    …" src="http://www.ad2ad.ir/showad.aspx?s=8&u=634914641388315473&p=tl"></script>

    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.

  • Error Line 353, Column 95: reference to entity "p" for which no system identifier could be generated
    …" src="http://www.ad2ad.ir/showad.aspx?s=8&u=634914641388315473&p=tl"></script>

    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 353, Column 93: entity was defined here
    …" src="http://www.ad2ad.ir/showad.aspx?s=8&u=634914641388315473&p=tl"></script>
  • Warning Line 359, Column 264: NET-enabling start-tag requires SHORTTAG YES
    …ontent/uploads/2012/12/ads.gif" alt="ariskar" width="120" height="120" /></a>';

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 728, Column 2: cannot generate system identifier for general entity "nbsp"
    &nbsp;</div>

    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 728, Column 2: general entity "nbsp" not defined and no default entity
    &nbsp;</div>

    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.

  • Error Line 728, Column 6: reference to entity "nbsp" for which no system identifier could be generated
    &nbsp;</div>

    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 728, Column 1: entity was defined here
    &nbsp;</div>
  • Error Line 732, Column 6: reference to entity "nbsp" for which no system identifier could be generated
    &nbsp;</div>

    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 728, Column 1: entity was defined here
    &nbsp;</div>
  • Error Line 737, Column 6: reference to entity "nbsp" for which no system identifier could be generated
    &nbsp;</div>

    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 728, Column 1: entity was defined here
    &nbsp;</div>
  • Warning Line 760, Column 6: NET-enabling start-tag requires SHORTTAG YES
    <br  />

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 769, 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
  • 5.833 visits

In Page Analysis