موقع قناة السومرية العراقية يعرض آخر اخبار العراق السياسية والاقتصادية والاجتماعية والمسلسلات العراقية والبرامج الترفيهية والفيديوهات والبث الحيّ. ...

alsumaria.tv
  • Domain Name
    alsumaria.tv
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #19833
  • Page Size
    274 KB
  • Ip Address
    216.151.213.200
  • Heading
    H1: 3, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    10 GIF, 33 JPG, 198 PNG

Website Meta Analysis

  • Title
    موقع قناة السومرية الفضائية العراقية | برامج واخبار العراق والعالم
  • Meta Keyword
    قناة،السومرية،العراقية،مقالات سياسية،اخبار العراق،اخبار عراقية،موقع قناة السومرية،طقس العراق،جاكلين عقيقي،بث حي،فيديو العراق،sumaria, alsumaria،السومريه
  • Meta Description
    موقع قناة السومرية العراقية يعرض آخر اخبار العراق السياسية والاقتصادية والاجتماعية والمسلسلات العراقية والبرامج الترفيهية والفيديوهات والبث الحيّ.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    216.151.213.200
  • Domain Age
    8 Years, 10 Months, 28 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from alsumaria.tv.

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 4.0.30319
  • x-powered-by: ASP.NET
  • date: Tue, 30 Jul 2013 15:32:03 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Tasjil
Mansourieh
Metn, Mount Lebanon 5555
LB
009614533344x1500
Fax:009614533344

Domain Name: ALSUMARIA.TV
Administrative Contact:
Faddoul, Jad email
Mansourieh
Metn, Mount Lebanon 5555
LB
009614533344x1500
Fax:009614533344

Technical Contact:
Faddoul, Jad email
Mansourieh
Metn, Mount Lebanon 5555
LB
009614533344x1500
Fax:009614533344

Updated: 06-02-2009 02:33:28 AM
Expires: 08-14-2015
Created: 08-14-2004
Name Servers:
NS2.INTERMEDIA.NET207.5.44.2
NS3.INTERMEDIA.NET207.5.1.222

DNS Analysis


DNS servers
ns2.intermedia.net [207.5.44.2]
ns3.intermedia.net [207.5.1.222]


DNS Records

Answer records
alsumaria.tv SOA
server: ns2.intermedia.net
email: hostmaster@intermedia.net
serial: 2012111501
refresh: 3600
retry: 3600
expire: 604800
minimum ttl: 600
100000s
alsumaria.tv NS  ns3.intermedia.net 600s
alsumaria.tv NS  ns2.intermedia.net 600s
alsumaria.tv A 216.151.213.200 100000s
alsumaria.tv MX
preference: 5
exchange: mail.alsumaria.tv
100000s
alsumaria.tv TXT v=spf1 include:spf.intermedia.net ~all 100000s
alsumaria.tv TXT 100000s

Authority records

Additional records
ns2.intermedia.net A 207.5.44.2 1000000s
ns3.intermedia.net A 207.5.1.222 1000000s
mail.alsumaria.tv A 38.96.174.198 100000s

IP 216.151.213.200 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    San Antonio
  • Continent Code
    78218
  • Latitude
    210
  • Longitude
    641
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 216.151.213.200"
    #
    # Use "?" to get help.
    #

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

    NetRange: 216.151.208.0 - 216.151.223.255
    CIDR: 216.151.208.0/20
    OriginAS:
    NetName: SERVER-ALLOC-2
    NetHandle: NET-216-151-208-0-1
    Parent: NET-216-0-0-0-0
    NetType: Direct Allocation
    RegDate: 2010-02-25
    Updated: 2012-03-02
    Ref: http://whois.arin.net/rest/net/NET-216-151-208-0-1

    OrgName: ServerBeach
    OrgId: SERVER-17
    Address: 8500 Vicar Drive 8500, Suite 500
    City: San Antonio
    StateProv: TX
    PostalCode: 78218
    Country: US
    RegDate: 2002-05-29
    Updated: 2012-05-14
    Ref: http://whois.arin.net/rest/org/SERVER-17

    OrgTechHandle: ZZ4092-ARIN
    OrgTechName: IP Admin
    OrgTechPhone: +1-210-225-4725
    OrgTechEmail: ipadmin@serverbeach.com
    OrgTechRef: http://whois.arin.net/rest/poc/ZZ4092-ARIN

    OrgAbuseHandle: SNAE-ARIN
    OrgAbuseName: Serverbeach Network AUP Enforcement
    OrgAbusePhone: +1-604-484-2588
    OrgAbuseEmail: abuse@serverbeach.com
    OrgAbuseRef: http://whois.arin.net/rest/poc/SNAE-ARIN

    RTechHandle: ZZ4092-ARIN
    RTechName: IP Admin
    RTechPhone: +1-210-225-4725
    RTechEmail: ipadmin@serverbeach.com
    RTechRef: http://whois.arin.net/rest/poc/ZZ4092-ARIN

    RNOCHandle: ZZ4092-ARIN
    RNOCName: IP Admin
    RNOCPhone: +1-210-225-4725
    RNOCEmail: ipadmin@serverbeach.com
    RNOCRef: http://whois.arin.net/rest/poc/ZZ4092-ARIN

    RAbuseHandle: SNAE-ARIN
    RAbuseName: Serverbeach Network AUP Enforcement
    RAbusePhone: +1-604-484-2588
    RAbuseEmail: abuse@serverbeach.com
    RAbuseRef: http://whois.arin.net/rest/poc/SNAE-ARIN

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 17 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.7232005074966232
Message Error
  • Error Line 58, Column 19: document type does not allow element "link" here
    rel="stylesheet" />

    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 61, Column 35: document type does not allow element "link" here
    rel="stylesheet" type="text/css" />

    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 63, Column 35: document type does not allow element "link" here
    rel="stylesheet" type="text/css" />

    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 65, Column 35: document type does not allow element "link" here
    rel="stylesheet" type="text/css" />

    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 103, Column 12: character "<" is the first character of a delimiter but occurred as data
    if (height < 44) {

    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 206, Column 534: there is no attribute "border"
    …ot;&quot;, true, &quot;LOGIN&quot;, &quot;&quot;, false, false))" border="0" />

    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 496, Column 35: document type does not allow element "link" here
    rel="stylesheet" type="text/css" />

    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 561, Column 28: character "&" is the first character of a delimiter but occurred as data
    		document.documentElement && document.documentElement.clientWidth ?

    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 561, Column 29: character "&" is the first character of a delimiter but occurred as data
    		document.documentElement && document.documentElement.clientWidth ?

    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 563, Column 50: character "&" is the first character of a delimiter but occurred as data
    … pageYOffset : document.documentElement && document.documentElement.scrollTop ?

    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 563, Column 51: character "&" is the first character of a delimiter but occurred as data
    … pageYOffset : document.documentElement && document.documentElement.scrollTop ?

    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 565, Column 13: character "<" is the first character of a delimiter but occurred as data
    if (this.sy < 0)

    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 566, Column 51: character "&" is the first character of a delimiter but occurred as data
    …nnerHeight : document.documentElement && document.documentElement.clientHeight…

    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 566, Column 52: character "&" is the first character of a delimiter but occurred as data
    …nerHeight : document.documentElement && document.documentElement.clientHeight …

    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 581, Column 24: character "<" is the first character of a delimiter but occurred as data
    if (eval(490 - scroll) < 100) {

    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 664, Column 100: there is no attribute "height"
    …"hpGuide1_dlWhatOnNow" cellspacing="0" cellpadding="0" border="0" height="245">

    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 882, Column 619: document type does not allow element "html" here
    …<![endif]--><!--[if !IE 8]><!--> <html><div class='hpNews_ContentDetails_title…

    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 882, Column 614: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    …e8'> <![endif]--><!--[if !IE 8]><!--> <html><div class='hpNews_ContentDetails_…

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

  • Error Line 882, Column 660: document type does not allow element "div" here
    …iv class='hpNews_ContentDetails_title'><!--<![endif]-->  <h3><a href='/news/70…

    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 882, Column 834: document type does not allow element "div" here
    …iv class='hpNews_ContentDetails_date' >الثلاثاء، 29 كانون الثاني 2013  17:06</…

    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 882, Column 932: document type does not allow element "div" here
    …ss='hpNews_ContentDetails_Description'>افاد مصدر في شرطة نينوى، الثلاثاء، بأن …

    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 882, Column 1019: "html" not finished but containing element ended
    … بهجوم مسلح شرق الموصل.</div>    </div>    <div class='hpNews_ContentDetails_r…
  • Error Line 882, Column 1019: end tag for "html" omitted, but OMITTAG NO was specified
    … بهجوم مسلح شرق الموصل.</div>    </div>    <div class='hpNews_ContentDetails_r…

    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 882, Column 614: start tag was here
    …e8'> <![endif]--><!--[if !IE 8]><!--> <html><div class='hpNews_ContentDetails_…
  • Error Line 882, Column 3859: document type does not allow element "html" here
    …<![endif]--><!--[if !IE 8]><!--> <html><div class='hpNews_ContentDetails_title…

    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 882, Column 3854: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    …e8'> <![endif]--><!--[if !IE 8]><!--> <html><div class='hpNews_ContentDetails_…

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

  • Error Line 882, Column 3900: document type does not allow element "div" here
    …iv class='hpNews_ContentDetails_title'><!--<![endif]-->  <h3><a href='/news/70…

    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 882, Column 4122: document type does not allow element "div" here
    …iv class='hpNews_ContentDetails_date' >الثلاثاء، 29 كانون الثاني 2013  17:13</…

    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 882, Column 4220: document type does not allow element "div" here
    …ss='hpNews_ContentDetails_Description'>عبر رئيس اقليم كردستان مسعود البارزاني،…

    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 882, Column 4347: "html" not finished but containing element ended
    …يرة التي شهدها الاقليم.</div>    </div>    <div class='hpNews_ContentDetails_r…
  • Error Line 882, Column 4347: end tag for "html" omitted, but OMITTAG NO was specified
    …يرة التي شهدها الاقليم.</div>    </div>    <div class='hpNews_ContentDetails_r…

    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 882, Column 3854: start tag was here
    …e8'> <![endif]--><!--[if !IE 8]><!--> <html><div class='hpNews_ContentDetails_…
  • Error Line 882, Column 7202: document type does not allow element "html" here
    …<![endif]--><!--[if !IE 8]><!--> <html><div class='hpNews_ContentDetails_title…

    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 882, Column 7197: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    …e8'> <![endif]--><!--[if !IE 8]><!--> <html><div class='hpNews_ContentDetails_…

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

  • Error Line 882, Column 7243: document type does not allow element "div" here
    …iv class='hpNews_ContentDetails_title'><!--<![endif]-->  <h3><a href='/news/70…

    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 882, Column 7458: document type does not allow element "div" here
    …iv class='hpNews_ContentDetails_date' >الثلاثاء، 29 كانون الثاني 2013  16:35</…

    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 882, Column 7556: document type does not allow element "div" here
    …ss='hpNews_ContentDetails_Description'>وافقت لجنة العلاقات الخارجية بمجلس الشي…

    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 882, Column 7689: "html" not finished but containing element ended
    … جون كيري لمنصب وزير...</div>    </div>    <div class='hpNews_ContentDetails_r…
  • Error Line 882, Column 7689: end tag for "html" omitted, but OMITTAG NO was specified
    … جون كيري لمنصب وزير...</div>    </div>    <div class='hpNews_ContentDetails_r…

    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 882, Column 7197: start tag was here
    …e8'> <![endif]--><!--[if !IE 8]><!--> <html><div class='hpNews_ContentDetails_…
  • Error Line 885, Column 8: required attribute "type" not specified
    <script>

    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 1012, Column 17: there is no attribute "href"
    <g:plusone href="http://www.alsumaria.tv/videos-on-Demand/videos/2584/alsumaria…

    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 1012, Column 94: there is no attribute "size"
    …nd/videos/2584/alsumaria-videos" size="small" annotation="none" width=""></g:p…

    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 1012, Column 113: there is no attribute "annotation"
    …eos/2584/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1012, Column 126: there is no attribute "width"
    …eos/2584/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1012, Column 128: element "g:plusone" undefined
    …eos/2584/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1074, Column 128: element "g:plusone" undefined
    …eos/2581/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1136, Column 128: element "g:plusone" undefined
    …eos/2585/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1198, Column 128: element "g:plusone" undefined
    …eos/2571/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1260, Column 128: element "g:plusone" undefined
    …eos/2572/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1322, Column 128: element "g:plusone" undefined
    …eos/2582/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1384, Column 128: element "g:plusone" undefined
    …eos/2583/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1446, Column 128: element "g:plusone" undefined
    …eos/2586/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1508, Column 128: element "g:plusone" undefined
    …eos/2580/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1570, Column 128: element "g:plusone" undefined
    …eos/2573/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1632, Column 128: element "g:plusone" undefined
    …eos/2579/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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 1694, Column 128: element "g:plusone" undefined
    …eos/2574/alsumaria-videos" size="small" annotation="none" width=""></g:plusone>

    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).
  • Warning Line 1815, Column 11: character "<" is the first character of a delimiter but occurred as data
    if (width < widthPolls) {

    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 1823, Column 23: character "<" is the first character of a delimiter but occurred as data
    if (eval(iPollsCount) <=  eval(3)) {

    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 1824, Column 17: character "<" is the first character of a delimiter but occurred as data
    if (iPollsCount < 10) {

    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 2098, Column 122: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …cHead"><div style="text-align: right;">حديثٌ من نوع آخر، مع ضيوف من نوع آخر...…

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 2298, Column 252: required attribute "alt" not specified
    …sImages/B-30-634903814057370931.jpg" height="100" width="300" border="0" /></a>

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

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

  • Error Line 2306, Column 279: required attribute "alt" not specified
    …sImages/B-34-634916982263065668.jpg" height="200" width="300" border="0" /></a>

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

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

  • Error Line 2321, Column 53: there is no attribute "profile_id"
    …                   <fb:fan profile_id=125165427541688 stream='1' connections='…

    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 2321, Column 53: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …                   <fb:fan profile_id=125165427541688 stream='1' connections='…
  • Error Line 2321, Column 76: there is no attribute "stream"
    …fan profile_id=125165427541688 stream='1' connections='0' logobar='0' height='…

    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 2321, Column 92: there is no attribute "connections"
    …25165427541688 stream='1' connections='0' logobar='0' height='350' width='300'…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 2321, Column 104: there is no attribute "logobar"
    …88 stream='1' connections='0' logobar='0' height='350' width='300'  css='http:…

    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 2321, Column 115: there is no attribute "height"
    …1' connections='0' logobar='0' height='350' width='300'  css='http://new.alsum…

    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 2321, Column 127: there is no attribute "width"
    …ns='0' logobar='0' height='350' width='300'  css='http://new.alsumaria.tv/styl…

    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 2321, Column 138: there is no attribute "css"
    …bar='0' height='350' width='300'  css='http://new.alsumaria.tv/style/FacebookF…

    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 2321, Column 192: element "fb:fan" undefined
    …dth='300'  css='http://new.alsumaria.tv/style/FacebookFanPage13.css' ></fb:fan>

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

Visitor Analysis

Daily Visitor
  • 10.617 visits