يوتيوب - يوتيوب فيديو - يوتيوب وادى الذئاب - موقع يوتيوب - مقاطع فيديو - يوتيوب مصارعة حرة - يوتيوب 2014 - يوتيوب 2013 - يوتيوب اون لاين ...

r2sa.net
  • Domain Name
    r2sa.net
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #50777
  • Page Size
    101.6 KB
  • Ip Address
    63.143.54.172
  • Heading
    H1: 0, H2: 32, H3: 12, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 64 JPG, 4 PNG

Website Meta Analysis

  • Title
    يوتيوب الرئاسة
  • Meta Keyword
    يوتيوب,يوتيوب youtube,يوتيوب فيديو,يوتيوب وادى الذئاب,موقع يوتيوب,فيديو مضحك,مقاطع فيديو,يوتيوب مصارعة حرة,يوتيوب اغاني,اغاني المصارعين
  • Meta Description
    يوتيوب - يوتيوب فيديو - يوتيوب وادى الذئاب - موقع يوتيوب - مقاطع فيديو - يوتيوب مصارعة حرة - يوتيوب 2014 - يوتيوب 2013 - يوتيوب اون لاين

Technical Analysis

  • Webserver
    nginx admin
  • Ip Address
    63.143.54.172
  • Domain Age
    4 Years, 6 Months, 7 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from r2sa.net.

HTML Analysis

  • server: nginx admin
  • date: Tue, 06 Aug 2013 15:31:25 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.2.17
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • x-cache: HIT from Backend
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for r2sa.net

DNS Analysis


DNS servers
ns1.r2sa.net [63.143.54.172]
ns2.r2sa.net [63.143.54.172]


DNS Records

Answer records
r2sa.net MX
preference: 0
exchange: a1759bfa6b6549897b5f03508d1fb3.pamx1.hotmail.com
14400s
r2sa.net SOA
server: ns1.r2sa.net
email: support@ultimateserv.com
serial: 2012120611
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 86400
86400s
r2sa.net NS  ns1.r2sa.net 86400s
r2sa.net NS  ns2.r2sa.net 86400s
r2sa.net A 63.143.54.172 14400s

Authority records

Additional records
ns1.r2sa.net A 63.143.54.172 14400s
ns2.r2sa.net A 63.143.54.172 14400s

IP 63.143.54.172 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • %rwhois V-1.5:003fff:00 rwhois.limestonenetworks.com (by Network Solutions, Inc. V-1.5.9.5)
    network:Class-Name:network
    network:ID:LSN-BLK-63.143.32.0/19
    network:Auth-Area:63.143.32.0/19
    network:Network-Name:LSN-63.143.32.0/19
    network:IP-Network:63.143.54.160/28
    network:IP-Network-Block:63.143.54.160 - 63.143.54.175
    network:Organization-Name:Hosny Mahmoud
    network:Organization-City:Mansoura
    network:Organization-State:OT
    network:Organization-Zip:35511
    network:Organization-Country:EG
    network:Tech-Contact;I:abuse@limestonenetworks.com
    network:Admin-Contact;I:abuse@limestonenetworks.com
    network:Updated-By:admin@limestonenetworks.com

    network:Class-Name:network
    network:ID:LSN-BLK-63.143.32.0/19
    network:Auth-Area:63.143.32.0/19
    network:Network-Name:LSN-63.143.32.0/19
    network:IP-Network:63.143.32.0/19
    network:IP-Network-Block:63.143.32.0 - 63.143.63.255
    network:Organization;I:Limestone Networks
    network:Tech-Contact;I:ipadmin@limestonenetworks.com
    network:Admin-Contact;I:admin@limestonenetworks.com
    network:Created:20080129
    network:Updated:20080129
    network:Updated-By:admin@limestonenetworks.com

    %referral rwhois://root.rwhois.net:4321/auth-area=.
    %ok

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 114 Errors
  • 110 Warnings
Ratio Text/Html
  • 0.6623673689066585
Message Error
  • Error Line 65, Column 47: there is no attribute "dir"
    …elopment by Hamdy Elfawey--><BODY dir="rtl" leftMargin=0 topMargin=0 oncontext…

    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 65, Column 64: there is no attribute "leftMargin"
    … Elfawey--><BODY dir="rtl" leftMargin=0 topMargin=0 oncontextmenu="return fals…

    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 65, Column 64: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … Elfawey--><BODY dir="rtl" leftMargin=0 topMargin=0 oncontextmenu="return fals…
  • Error Line 65, Column 76: there is no attribute "topMargin"
    …BODY dir="rtl" leftMargin=0 topMargin=0 oncontextmenu="return false" ondragsta…

    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 65, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …BODY dir="rtl" leftMargin=0 topMargin=0 oncontextmenu="return false" ondragsta…
  • Error Line 65, Column 92: there is no attribute "oncontextmenu"
    …eftMargin=0 topMargin=0 oncontextmenu="return false" ondragstart="return false…

    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 65, Column 119: there is no attribute "ondragstart"
    …ontextmenu="return false" ondragstart="return false" onselectstart="return fal…

    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 65, Column 148: there is no attribute "onselectstart"
    …ragstart="return false" onselectstart="return false"></body></html><!-- Develo…

    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 65, Column 162: element "BODY" undefined
    …rn false" onselectstart="return false"></body></html><!-- Development by Hamdy…

    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 65, Column 169: end tag for element "body" which is not open
    …e" onselectstart="return false"></body></html><!-- Development by Hamdy Elfawe…

    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 65, Column 176: end tag for "BODY" omitted, but OMITTAG NO was specified
    …onselectstart="return false"></body></html><!-- Development by Hamdy Elfawey-->

    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 65, Column 37: start tag was here
    <!-- Development by Hamdy Elfawey--><BODY dir="rtl" leftMargin=0 topMargin=0 on…
  • Error Line 65, Column 176: end tag for "html" which is not finished
    …onselectstart="return false"></body></html><!-- Development by Hamdy Elfawey-->

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 67, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Warning Line 72, Column 15: character "<" is the first character of a delimiter but occurred as data
    for (i = 0; i < omitformtags.length; i++)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 87, Column 15: character "<" is the first character of a delimiter but occurred as data
    for (j = 0; j < tags.length; j++){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 88, Column 15: character "<" is the first character of a delimiter but occurred as data
    for (i = 0; i < omitformtags.length; i++)

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 106, Column 38: document type does not allow element "body" here
    </script><body class="home" id="home">

    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 118, Column 142: required attribute "alt" not specified
    …rss.php"><img src="../link.png" width="33" height="33" border="0" /></a></span>

    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 119, Column 162: required attribute "alt" not specified
    …g" width="33" height="33" border="0" /></a></span><span style="float:left; mar…

    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 119, Column 332: required attribute "alt" not specified
    …G"><img src="../link.png" width="33" height="33" border="0" /></a></span></div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 150, Column 336: there is no attribute "allowTransparency"
    …overflow:hidden; width:180px; height:170px;" allowTransparency="true"></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 183, Column 23: document type does not allow element "div" here; assuming missing "li" start-tag
    <div class="headerbar"><a href="http://www.r2sa.net/file.php?f=2986">فيلم وادى …
  • Error Line 195, Column 11: end tag for "li" omitted, but OMITTAG NO was specified
          </ol>

    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 183, Column 1: start tag was here
    <div class="headerbar"><a href="http://www.r2sa.net/file.php?f=2986">فيلم وادى …
  • Error Line 1082, Column 12: ID "side_menu" already defined
      <div id="side_menu">

    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 134, Column 18: ID "side_menu" first defined here
      </div><div id="side_menu">
  • Error Line 2101, Column 5: document type does not allow element "div" here; assuming missing "li" start-tag
    <div>
  • Error Line 2102, Column 75: there is no attribute "alt"
    …p://www.r2sa.net/file.php?f=6248" alt="ذا روك يهزم سى ام بانك وينافس جون سينا …

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

    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 2117, Column 1: start tag was here
    <div>
  • Error Line 2119, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
          </ol>

    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 2115, Column 1: start tag was here
    <div>
  • Error Line 2119, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
          </ol>

    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 2113, Column 1: start tag was here
    <div>
  • Error Line 2119, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
          </ol>

    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 2111, Column 1: start tag was here
    <div>
  • Error Line 2119, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
          </ol>

    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 2109, Column 1: start tag was here
    <div>
  • Error Line 2119, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
          </ol>

    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 2107, Column 1: start tag was here
    <div>
  • Error Line 2119, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
          </ol>

    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 2105, Column 1: start tag was here
    <div>
  • Error Line 2119, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
          </ol>

    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 2103, Column 1: start tag was here
    <div>
  • Error Line 2119, Column 11: end tag for "div" omitted, but OMITTAG NO was specified
          </ol>

    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 2101, Column 1: start tag was here
    <div>
  • Error Line 2119, Column 11: end tag for "li" omitted, but OMITTAG NO was specified
          </ol>

    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 2101, Column 1: start tag was here
    <div>
  • Warning Line 2150, Column 51: cannot generate system identifier for general entity "p"
    …f="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a></…

    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 2150, Column 51: general entity "p" not defined and no default entity
    …f="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a></…

    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 2150, Column 52: reference not terminated by REFC delimiter
    …="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a></l…

    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 2150, Column 52: reference to external entity in attribute value
    …="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a></l…

    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 2150, Column 52: reference to entity "p" for which no system identifier could be generated
    …="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a></l…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2151, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=18&p=1" target="_blank">وادى الذئاب 2</a></l…

    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 2151, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=18&p=1" target="_blank">وادى الذئاب 2</a></l…

    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 2151, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=18&p=1" target="_blank">وادى الذئاب 2</a></l…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2152, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=19&p=1" target="_blank">وادى الذئاب 3</a></l…

    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 2152, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=19&p=1" target="_blank">وادى الذئاب 3</a></l…

    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 2152, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=19&p=1" target="_blank">وادى الذئاب 3</a></l…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2153, Column 52: reference not terminated by REFC delimiter
    …="http://www.r2sa.net/browse.php?c=2&p=1" target="_blank">وادى الذئاب 4</a></l…

    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 2153, Column 52: reference to external entity in attribute value
    …="http://www.r2sa.net/browse.php?c=2&p=1" target="_blank">وادى الذئاب 4</a></l…

    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 2153, Column 52: reference to entity "p" for which no system identifier could be generated
    …="http://www.r2sa.net/browse.php?c=2&p=1" target="_blank">وادى الذئاب 4</a></l…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2154, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=28&p=1" target="_blank">وادى الذئاب 5</a></l…

    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 2154, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=28&p=1" target="_blank">وادى الذئاب 5</a></l…

    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 2154, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=28&p=1" target="_blank">وادى الذئاب 5</a></l…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2159, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=55&p=1" target="_blank">وادى الذئاب 6 مترجم<…

    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 2159, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=55&p=1" target="_blank">وادى الذئاب 6 مترجم<…

    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 2159, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=55&p=1" target="_blank">وادى الذئاب 6 مترجم<…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2160, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=56&p=1" target="_blank">وادى الذئاب 6 مدبلج<…

    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 2160, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=56&p=1" target="_blank">وادى الذئاب 6 مدبلج<…

    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 2160, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=56&p=1" target="_blank">وادى الذئاب 6 مدبلج<…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2161, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=61&p=1" target="_blank">وادى الذئاب 7 مترجم<…

    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 2161, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=61&p=1" target="_blank">وادى الذئاب 7 مترجم<…

    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 2161, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=61&p=1" target="_blank">وادى الذئاب 7 مترجم<…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2162, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=67&p=1" target="_blank">صور وادى الذئاب</a><…

    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 2162, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=67&p=1" target="_blank">صور وادى الذئاب</a><…

    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 2162, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=67&p=1" target="_blank">صور وادى الذئاب</a><…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2163, Column 52: reference not terminated by REFC delimiter
    …="http://www.r2sa.net/browse.php?c=3&p=1" target="_blank">اغانى وادى الذئاب</a…

    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 2163, Column 52: reference to external entity in attribute value
    …="http://www.r2sa.net/browse.php?c=3&p=1" target="_blank">اغانى وادى الذئاب</a…

    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 2163, Column 52: reference to entity "p" for which no system identifier could be generated
    …="http://www.r2sa.net/browse.php?c=3&p=1" target="_blank">اغانى وادى الذئاب</a…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2167, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=65&p=1" target="_blank">اخبار المصارعة الحرة…

    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 2167, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=65&p=1" target="_blank">اخبار المصارعة الحرة…

    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 2167, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=65&p=1" target="_blank">اخبار المصارعة الحرة…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2168, Column 52: reference not terminated by REFC delimiter
    …="http://www.r2sa.net/browse.php?c=4&p=1" target="_blank">المصارعة الحرة</a></…

    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 2168, Column 52: reference to external entity in attribute value
    …="http://www.r2sa.net/browse.php?c=4&p=1" target="_blank">المصارعة الحرة</a></…

    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 2168, Column 52: reference to entity "p" for which no system identifier could be generated
    …="http://www.r2sa.net/browse.php?c=4&p=1" target="_blank">المصارعة الحرة</a></…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2169, Column 52: reference not terminated by REFC delimiter
    …="http://www.r2sa.net/browse.php?c=4&p=1" target="_blank">مصارعة حرة 2013</a><…

    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 2169, Column 52: reference to external entity in attribute value
    …="http://www.r2sa.net/browse.php?c=4&p=1" target="_blank">مصارعة حرة 2013</a><…

    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 2169, Column 52: reference to entity "p" for which no system identifier could be generated
    …="http://www.r2sa.net/browse.php?c=4&p=1" target="_blank">مصارعة حرة 2013</a><…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2170, Column 52: reference not terminated by REFC delimiter
    …="http://www.r2sa.net/browse.php?c=5&p=1" target="_blank">اغانى المصارعين</a><…

    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 2170, Column 52: reference to external entity in attribute value
    …="http://www.r2sa.net/browse.php?c=5&p=1" target="_blank">اغانى المصارعين</a><…

    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 2170, Column 52: reference to entity "p" for which no system identifier could be generated
    …="http://www.r2sa.net/browse.php?c=5&p=1" target="_blank">اغانى المصارعين</a><…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2171, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=66&p=1" target="_blank">صور المصارعة الحرة</…

    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 2171, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=66&p=1" target="_blank">صور المصارعة الحرة</…

    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 2171, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=66&p=1" target="_blank">صور المصارعة الحرة</…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2175, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=59&p=1" target="_blank">برنامج سحر الدنيا</a…

    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 2175, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=59&p=1" target="_blank">برنامج سحر الدنيا</a…

    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 2175, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=59&p=1" target="_blank">برنامج سحر الدنيا</a…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2176, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=58&p=1" target="_blank">عمر صانع الحضارة</a>…

    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 2176, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=58&p=1" target="_blank">عمر صانع الحضارة</a>…

    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 2176, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=58&p=1" target="_blank">عمر صانع الحضارة</a>…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2177, Column 53: reference not terminated by REFC delimiter
    …="http://www.r2sa.net/browse.php?c=46&p=1" target="_blank">يوتيوب مضحك</a></li>

    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 2177, Column 53: reference to external entity in attribute value
    …="http://www.r2sa.net/browse.php?c=46&p=1" target="_blank">يوتيوب مضحك</a></li>

    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 2177, Column 53: reference to entity "p" for which no system identifier could be generated
    …="http://www.r2sa.net/browse.php?c=46&p=1" target="_blank">يوتيوب مضحك</a></li>

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2178, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=31&p=1" target="_blank">يوتيوب منوعات</a></l…

    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 2178, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=31&p=1" target="_blank">يوتيوب منوعات</a></l…

    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 2178, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=31&p=1" target="_blank">يوتيوب منوعات</a></l…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2179, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=36&p=1" target="_blank">يوتيوب سيارات</a></l…

    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 2179, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=36&p=1" target="_blank">يوتيوب سيارات</a></l…

    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 2179, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=36&p=1" target="_blank">يوتيوب سيارات</a></l…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2183, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=25&p=1" target="_blank">يوتيوب اناشيد</a></l…

    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 2183, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=25&p=1" target="_blank">يوتيوب اناشيد</a></l…

    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 2183, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=25&p=1" target="_blank">يوتيوب اناشيد</a></l…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2184, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=49&p=1" target="_blank">اناشيد طيور الجنة</a…

    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 2184, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=49&p=1" target="_blank">اناشيد طيور الجنة</a…

    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 2184, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=49&p=1" target="_blank">اناشيد طيور الجنة</a…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2185, Column 53: reference not terminated by REFC delimiter
    …ref="http://www.r2sa.net/browse.php?c=16&p=1" target="_blank">اسلاميات</a></li>

    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 2185, Column 53: reference to external entity in attribute value
    …ref="http://www.r2sa.net/browse.php?c=16&p=1" target="_blank">اسلاميات</a></li>

    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 2185, Column 53: reference to entity "p" for which no system identifier could be generated
    …ref="http://www.r2sa.net/browse.php?c=16&p=1" target="_blank">اسلاميات</a></li>

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2186, Column 53: reference not terminated by REFC delimiter
    …href="http://www.r2sa.net/browse.php?c=12&p=1" target="_blank">كرة قدم</a></li>

    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 2186, Column 53: reference to external entity in attribute value
    …href="http://www.r2sa.net/browse.php?c=12&p=1" target="_blank">كرة قدم</a></li>

    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 2186, Column 53: reference to entity "p" for which no system identifier could be generated
    …href="http://www.r2sa.net/browse.php?c=12&p=1" target="_blank">كرة قدم</a></li>

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2187, Column 53: reference not terminated by REFC delimiter
    …f="http://www.r2sa.net/browse.php?c=45&p=1" target="_blank">يوتيوب طبخ</a></li>

    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 2187, Column 53: reference to external entity in attribute value
    …f="http://www.r2sa.net/browse.php?c=45&p=1" target="_blank">يوتيوب طبخ</a></li>

    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 2187, Column 53: reference to entity "p" for which no system identifier could be generated
    …f="http://www.r2sa.net/browse.php?c=45&p=1" target="_blank">يوتيوب طبخ</a></li>

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2191, Column 53: reference not terminated by REFC delimiter
    …a href="http://www.r2sa.net/browse.php?c=15&p=1" target="_blank">كرتون</a></li>

    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 2191, Column 53: reference to external entity in attribute value
    …a href="http://www.r2sa.net/browse.php?c=15&p=1" target="_blank">كرتون</a></li>

    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 2191, Column 53: reference to entity "p" for which no system identifier could be generated
    …a href="http://www.r2sa.net/browse.php?c=15&p=1" target="_blank">كرتون</a></li>

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2192, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=33&p=1" target="_blank">كرتون سبونج بوب</a><…

    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 2192, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=33&p=1" target="_blank">كرتون سبونج بوب</a><…

    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 2192, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=33&p=1" target="_blank">كرتون سبونج بوب</a><…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2193, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=26&p=1" target="_blank">كرتون ون بيس</a></li…

    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 2193, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=26&p=1" target="_blank">كرتون ون بيس</a></li…

    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 2193, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=26&p=1" target="_blank">كرتون ون بيس</a></li…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2194, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=39&p=1" target="_blank">كرتون سلام دانك</a><…

    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 2194, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=39&p=1" target="_blank">كرتون سلام دانك</a><…

    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 2194, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=39&p=1" target="_blank">كرتون سلام دانك</a><…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Warning Line 2195, Column 53: reference not terminated by REFC delimiter
    …"http://www.r2sa.net/browse.php?c=68&p=1" target="_blank">منوعات | عالم الصور<…

    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 2195, Column 53: reference to external entity in attribute value
    …"http://www.r2sa.net/browse.php?c=68&p=1" target="_blank">منوعات | عالم الصور<…

    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 2195, Column 53: reference to entity "p" for which no system identifier could be generated
    …"http://www.r2sa.net/browse.php?c=68&p=1" target="_blank">منوعات | عالم الصور<…

    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 2150, Column 50: entity was defined here
    …ef="http://www.r2sa.net/browse.php?c=1&p=1" target="_blank">وادى الذئاب 1</a><…
  • Error Line 2229, Column 7: end tag for "div" omitted, but OMITTAG NO was specified
    </body>

    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 108, Column 1: start tag was here
    <div id="main_body">
  • Error Line 2231, 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.

Visitor Analysis

Daily Visitor
  • 1.167 visits