azdrama.net

watch online, download free, hk drama, hk show, hk movies, tvb drama, tvb show, korean drama, chinese drama, taiwanese drama ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    azdrama.net
  • Favicon
  • Alexa Rank
    #6025
  • Google Page Rank
    PR 4
  • Ip Address
    37.220.34.27
  • Page Size
    45.2 KB
  • Images
    0 GIF, 10 JPG, 20 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    20 1 1 0 0 0

Website Meta Analysis



  • Title
    Watch online and download free Asian drama, movies, shows
  • Meta Keyword
    watch online, download free, hk drama, hk show, hk movies, tvb drama, tvb show, korean drama, asian drama, online streaming, chinese drama, taiwanese drama, full movies online,play movies online,movies online,full films online,watch full videos online, azdrama, azdrama.net
  • Meta Description
    watch online, download free, hk drama, hk show, hk movies, tvb drama, tvb show, korean drama, chinese drama, taiwanese drama

Technical Analysis



  • Webserver
    Apache/2.2.15
  • Ip Address
    37.220.34.27
  • Domain Age
    2 Years, 8 Months, 25 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Sun, 16 Jun 2013 16:04:22 GMT
  • server: Apache/2.2.15
  • x-powered-by: PHP/5.3.3
  • 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
  • content-encoding: gzip
  • vary: Accept-Encoding
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: azdrama.net
Registrar: Name.com LLC

Protected Domain Services Customer ID: NCR-2775035

Expiration Date: 2013-10-05 07:07:32
Creation Date: 2010-10-05 07:07:32

Name Servers:
ns1dhq.name.com
ns2jrt.name.com
ns3qtx.name.com
ns4dfh.name.com

Domain privacy provided by Protected Domain Services. For more information see www.protecteddomainservices.com

REGISTRANT CONTACT INFO
Protected Domain Services - Customer ID: NCR-2775035
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.3037474010
Email Address: email

ADMINISTRATIVE CONTACT INFO
Protected Domain Services - Customer ID: NCR-2775035
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.3037474010
Email Address: email

TECHNICAL CONTACT INFO
Protected Domain Services - Customer ID: NCR-2775035
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.3037474010
Email Address: email

BILLING CONTACT INFO
Protected Domain Services - Customer ID: NCR-2775035
P.O. Box 6197
Denver
CO
80206
US
Phone: +1.3037474010
Email Address: email

DNS Analysis


DNS servers
ns1dhq.name.com [184.172.59.24]
ns2jrt.name.com [5.153.6.206]
ns3qtx.name.com [208.43.116.47]
ns4dfh.name.com [174.129.224.234]


DNS Records

Answer records
azdrama.net NS  ns4dfh.name.com 300s
azdrama.net A 37.220.34.27 300s
azdrama.net NS  ns3qtx.name.com 300s
azdrama.net NS  ns1dhq.name.com 300s
azdrama.net SOA
server: ns1dhq.name.com
email: support@name.com
serial: 1
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
300s
azdrama.net NS  ns2jrt.name.com 300s

Authority records

Additional records
ns2jrt.name.com A 5.153.6.206 86400s
ns3qtx.name.com A 208.43.116.47 86400s
ns4dfh.name.com A 174.129.224.234 86400s
ns1dhq.name.com A 184.172.59.24 86400s

IP 37.220.34.27 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 86 Errors
  • 22 Warnings
Ratio Text/Html
  • 0.6902469562213971
Message Error
  • Error Line 19, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

  • Warning Line 23, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=234148183301331";

    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 23, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=234148183301331";

    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 23, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=234148183301331";

    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.

  • Error Line 23, Column 62: reference to entity "appId" for which no system identifier could be generated
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=234148183301331";

    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 23, Column 56: entity was defined here
      js.src = "//connect.facebook.net/en_US/all.js#xfbml=1&appId=234148183301331";
  • Error Line 29, Column 342: end tag for "input" omitted, but OMITTAG NO was specified
    …value = 'Looking for something...';}"><input type="hidden" name="searchbutton"…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 29, Column 107: start tag was here
    …action="http://azdrama.net/index.php"><input name="kw" id="kw" class="default"…
  • Warning Line 41, Column 56: cannot generate system identifier for general entity "sort"
    …><a href="http://azdrama.net/english/&sort=date" title="English subtitle drama…

    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 41, Column 56: general entity "sort" not defined and no default entity
    …><a href="http://azdrama.net/english/&sort=date" title="English subtitle drama…

    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 41, Column 60: reference not terminated by REFC delimiter
    …href="http://azdrama.net/english/&sort=date" title="English subtitle drama & m…

    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 41, Column 60: reference to external entity in attribute value
    …href="http://azdrama.net/english/&sort=date" title="English subtitle drama & m…

    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 41, Column 60: reference to entity "sort" for which no system identifier could be generated
    …href="http://azdrama.net/english/&sort=date" title="English subtitle drama & m…

    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 41, Column 55: entity was defined here
    …"><a href="http://azdrama.net/english/&sort=date" title="English subtitle dram…
  • Warning Line 41, Column 97: character "&" is the first character of a delimiter but occurred as data
    …t=date" title="English subtitle drama & movies list"><s></s>English Subtitle</…

    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 44, Column 43: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … id="mynewads_01"><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling…
  • Error Line 44, Column 57: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …01"><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=728 …
  • Error Line 44, Column 72: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=728 height=90 src="…
  • Error Line 44, Column 84: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=728 height=90 src="http://adser…
  • Error Line 44, Column 93: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=728 height=90 src="http://adserving.cpxi…
  • Error Line 44, Column 104: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=728 height=90 src="http://adserving.cpxinteractive.…
  • Warning Line 44, Column 166: cannot generate system identifier for general entity "ad_size"
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe…

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

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

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

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

  • Error Line 44, Column 166: general entity "ad_size" not defined and no default entity
    ….cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe…

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

  • Warning Line 44, Column 173: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span…

    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 44, Column 173: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span…

    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 44, Column 173: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span…

    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 44, Column 165: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></ifram…
  • Warning Line 44, Column 181: cannot generate system identifier for general entity "section"
    ….com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span style="…

    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 44, Column 181: general entity "section" not defined and no default entity
    ….com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span style="…

    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 44, Column 188: reference not terminated by REFC delimiter
    …?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span style="float:r…

    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 44, Column 188: reference to external entity in attribute value
    …?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span style="float:r…

    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 44, Column 188: reference to entity "section" for which no system identifier could be generated
    …?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span style="float:r…

    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 44, Column 180: entity was defined here
    …e.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span style=…
  • Error Line 81, Column 91: document type does not allow element "a" here; assuming missing "li" start-tag
    …ly-fire/" title="Friendly Fire - 法網狙擊"><img width="115px;" src="http://azdrama…
  • Error Line 84, Column 210: end tag for "img" omitted, but OMITTAG NO was specified
    …s/icon_download.png" alt="Download Friendly Fire - 法網狙擊" border="0"></a></span>

    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 84, Column 96: start tag was here
    …k-drama/1095-friendly-fire/download/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 85, Column 201: end tag for "img" omitted, but OMITTAG NO was specified
    …p/images/tv.png" alt="Watch online Friendly Fire - 法網狙擊" border="0"></a></span>

    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 85, Column 94: start tag was here
    …ama/1095-friendly-fire/list-episode/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 103, Column 220: end tag for "img" omitted, but OMITTAG NO was specified
    …download.png" alt="Download Inbound Troubles - 老表, 你好嘢!" border="0"></a></span>

    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 103, Column 99: start tag was here
    …rama/1135-inbound-troubles/download/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 104, Column 211: end tag for "img" omitted, but OMITTAG NO was specified
    …s/tv.png" alt="Watch online Inbound Troubles - 老表, 你好嘢!" border="0"></a></span>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 104, Column 97: start tag was here
    …/1135-inbound-troubles/list-episode/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 121, Column 211: end tag for "img" omitted, but OMITTAG NO was specified
    …/icon_download.png" alt="Download Come Home Love - 愛.回家" border="0"></a></span>

    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 121, Column 96: start tag was here
    …k-drama/835-come-home-love/download/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 122, Column 202: end tag for "img" omitted, but OMITTAG NO was specified
    …/images/tv.png" alt="Watch online Come Home Love - 愛.回家" border="0"></a></span>

    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 122, Column 94: start tag was here
    …ama/835-come-home-love/list-episode/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 140, Column 207: end tag for "img" omitted, but OMITTAG NO was specified
    …es/icon_download.png" alt="Download Missing You - 幸福摩天輪" border="0"></a></span>

    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 140, Column 94: start tag was here
    …/hk-drama/1094-missing-you/download/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 141, Column 198: end tag for "img" omitted, but OMITTAG NO was specified
    …mp/images/tv.png" alt="Watch online Missing You - 幸福摩天輪" border="0"></a></span>

    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 141, Column 92: start tag was here
    …drama/1094-missing-you/list-episode/"><img src="http://azdrama.net/skin/tmp/im…
  • Warning Line 143, Column 35: character "&" is the first character of a delimiter but occurred as data
    				<div align="justify">A Search & Rescue agency specializes in finding loved …

    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 159, Column 209: end tag for "img" omitted, but OMITTAG NO was specified
    …es/icon_download.png" alt="Download The Confidant - 大太監" border="0"></a></span>

    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 159, Column 96: start tag was here
    …k-drama/1028-the-confidant/download/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 160, Column 200: end tag for "img" omitted, but OMITTAG NO was specified
    …mp/images/tv.png" alt="Watch online The Confidant - 大太監" border="0"></a></span>

    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 160, Column 94: start tag was here
    …ama/1028-the-confidant/list-episode/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 179, Column 245: end tag for "img" omitted, but OMITTAG NO was specified
    …g" alt="Download Silver Spoon, Sterling Shackles - 名媛望族" border="0"></a></span>

    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 179, Column 113: start tag was here
    …er-spoon-sterling-shackles/download/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 180, Column 236: end tag for "img" omitted, but OMITTAG NO was specified
    …lt="Watch online Silver Spoon, Sterling Shackles - 名媛望族" border="0"></a></span>

    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 180, Column 111: start tag was here
    …poon-sterling-shackles/list-episode/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 199, Column 211: end tag for "img" omitted, but OMITTAG NO was specified
    …/icon_download.png" alt="Download Highs and Lows - 雷霆掃毒" border="0"></a></span>

    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 199, Column 96: start tag was here
    …k-drama/981-highs-and-lows/download/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 200, Column 202: end tag for "img" omitted, but OMITTAG NO was specified
    …/images/tv.png" alt="Watch online Highs and Lows - 雷霆掃毒" border="0"></a></span>

    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 200, Column 94: start tag was here
    …ama/981-highs-and-lows/list-episode/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 216, Column 223: end tag for "img" omitted, but OMITTAG NO was specified
    …_download.png" alt="Download The Last Steep Ascent - 天梯" border="0"></a></span>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 216, Column 103: start tag was here
    …/970-the-last-steep-ascent/download/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 217, Column 214: end tag for "img" omitted, but OMITTAG NO was specified
    …es/tv.png" alt="Watch online The Last Steep Ascent - 天梯" border="0"></a></span>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 217, Column 101: start tag was here
    …-the-last-steep-ascent/list-episode/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 235, Column 218: end tag for "img" omitted, but OMITTAG NO was specified
    …n_download.png" alt="Download Divas in Distress - 巴不得媽媽" border="0"></a></span>

    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 235, Column 99: start tag was here
    …rama/948-divas-in-distress/download/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 236, Column 209: end tag for "img" omitted, but OMITTAG NO was specified
    …ges/tv.png" alt="Watch online Divas in Distress - 巴不得媽媽" border="0"></a></span>

    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 236, Column 97: start tag was here
    …/948-divas-in-distress/list-episode/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 254, Column 202: end tag for "img" omitted, but OMITTAG NO was specified
    …mages/icon_download.png" alt="Download King Maker - 造王者" border="0"></a></span>

    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 254, Column 92: start tag was here
    …et/hk-drama/930-king-maker/download/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 255, Column 193: end tag for "img" omitted, but OMITTAG NO was specified
    …n/tmp/images/tv.png" alt="Watch online King Maker - 造王者" border="0"></a></span>

    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 255, Column 90: start tag was here
    …k-drama/930-king-maker/list-episode/"><img src="http://azdrama.net/skin/tmp/im…
  • Error Line 269, Column 42: end tag for "li" omitted, but OMITTAG NO was specified
    …	<h1 class="moviemaker-list"></h1></ul><div class="clear"></div></div></div></…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 81, Column 5: start tag was here
    				<a href="http://azdrama.net/hk-drama/1095-friendly-fire/" title="Friendly F…
  • Error Line 275, Column 47: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id ="mynewads_02"><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling…
  • Error Line 275, Column 61: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …02"><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 …
  • Error Line 275, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 height=250 src=…
  • Error Line 275, Column 88: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=300 height=250 src="http://ads.…
  • Error Line 275, Column 97: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=300 height=250 src="http://ads.harrenmed…
  • Error Line 275, Column 108: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=300 height=250 src="http://ads.harrenmedianetwork.c…
  • Warning Line 275, Column 176: reference not terminated by REFC delimiter
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div…

    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 275, Column 176: reference to external entity in attribute value
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div…

    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 275, Column 176: reference to entity "ad_size" for which no system identifier could be generated
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div…

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

  • Info Line 44, Column 165: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></ifram…
  • Warning Line 275, Column 192: reference not terminated by REFC delimiter
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div>

    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 275, Column 192: reference to external entity in attribute value
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div>

    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 275, Column 192: reference to entity "section" for which no system identifier could be generated
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div>

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

  • Info Line 44, Column 180: entity was defined here
    …e.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span style=…
  • Error Line 291, Column 39: there is no attribute "data-href"
    			<div class="fb-like-box" data-href="http://www.facebook.com/azdrama" data-wi…

    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 291, Column 84: there is no attribute "data-width"
    …/www.facebook.com/azdrama" data-width="300" data-height="260" data-show-faces=…

    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 291, Column 102: there is no attribute "data-height"
    …azdrama" data-width="300" data-height="260" data-show-faces="true" data-stream…

    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 291, Column 124: there is no attribute "data-show-faces"
    …00" data-height="260" data-show-faces="true" data-stream="false" data-header="…

    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 291, Column 143: there is no attribute "data-stream"
    …ght="260" data-show-faces="true" data-stream="false" data-header="false"></div>

    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 291, Column 163: there is no attribute "data-header"
    …ght="260" data-show-faces="true" data-stream="false" data-header="false"></div>

    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 292, Column 47: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id ="mynewads_03"><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling…
  • Error Line 292, Column 61: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …03"><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 …
  • Error Line 292, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 height=250 src=…
  • Error Line 292, Column 88: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=300 height=250 src="http://adse…
  • Error Line 292, Column 97: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=300 height=250 src="http://adserving.cpx…
  • Error Line 292, Column 108: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=300 height=250 src="http://adserving.cpxinteractive…
  • Warning Line 292, Column 178: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=1845071"></iframe></div…

    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 292, Column 178: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=1845071"></iframe></div…

    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 292, Column 178: reference to entity "ad_size" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=1845071"></iframe></div…

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

  • Info Line 44, Column 165: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></ifram…
  • Warning Line 292, Column 194: reference not terminated by REFC delimiter
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=1845071"></iframe></div>

    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 292, Column 194: reference to external entity in attribute value
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=1845071"></iframe></div>

    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 292, Column 194: reference to entity "section" for which no system identifier could be generated
    …eractive.com/st?ad_type=iframe&ad_size=300x250&section=1845071"></iframe></div>

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

  • Info Line 44, Column 180: entity was defined here
    …e.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span style=…
  • Error Line 293, Column 47: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …id ="mynewads_04"><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling…
  • Error Line 293, Column 61: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …04"><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 …
  • Error Line 293, Column 76: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=no width=300 height=250 src=…
  • Error Line 293, Column 88: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=no width=300 height=250 src="http://ads.…
  • Error Line 293, Column 97: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=no width=300 height=250 src="http://ads.harrenmed…
  • Error Line 293, Column 108: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=no width=300 height=250 src="http://ads.harrenmedianetwork.c…
  • Warning Line 293, Column 176: reference not terminated by REFC delimiter
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div…

    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 293, Column 176: reference to external entity in attribute value
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div…

    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 293, Column 176: reference to entity "ad_size" for which no system identifier could be generated
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div…

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

  • Info Line 44, Column 165: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></ifram…
  • Warning Line 293, Column 192: reference not terminated by REFC delimiter
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div>

    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 293, Column 192: reference to external entity in attribute value
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div>

    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 293, Column 192: reference to entity "section" for which no system identifier could be generated
    …anetwork.com/st?ad_type=iframe&ad_size=300x250&section=1871072"></iframe></div>

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

  • Info Line 44, Column 180: entity was defined here
    …e.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span style=…
  • Error Line 294, Column 56: required attribute "type" not specified
    …ttp://widgets.twimg.com/j/2/widget.js"></script><script>new TWTR.Widget({versi…

    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 294, Column 73: required attribute "type" not specified
    …mg.com/j/2/widget.js"></script><script>new TWTR.Widget({version:2,type:'profil…

    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 301, Column 81: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    … id="mynewads_06"><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling…
  • Error Line 301, Column 95: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …06"><iframe frameborder=0 marginwidth=0 marginheight=0 scrolling=NO width=728 …
  • Error Line 301, Column 110: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …meborder=0 marginwidth=0 marginheight=0 scrolling=NO width=728 height=90 src="…
  • Error Line 301, Column 122: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …arginwidth=0 marginheight=0 scrolling=NO width=728 height=90 src="http://ads.h…
  • Error Line 301, Column 122: value of attribute "scrolling" cannot be "NO"; must be one of "yes", "no", "auto"
    …arginwidth=0 marginheight=0 scrolling=NO width=728 height=90 src="http://ads.h…

    The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

  • Error Line 301, Column 131: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …h=0 marginheight=0 scrolling=NO width=728 height=90 src="http://ads.harrenmedi…
  • Error Line 301, Column 142: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …eight=0 scrolling=NO width=728 height=90 src="http://ads.harrenmedianetwork.co…
  • Warning Line 301, Column 209: reference not terminated by REFC delimiter
    …anetwork.com/st?ad_type=iframe&ad_size=728x90&section=1871072"></iframe></div>…

    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 301, Column 209: reference to external entity in attribute value
    …anetwork.com/st?ad_type=iframe&ad_size=728x90&section=1871072"></iframe></div>…

    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 301, Column 209: reference to entity "ad_size" for which no system identifier could be generated
    …anetwork.com/st?ad_type=iframe&ad_size=728x90&section=1871072"></iframe></div>…

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

  • Info Line 44, Column 165: entity was defined here
    …g.cpxinteractive.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></ifram…
  • Warning Line 301, Column 224: reference not terminated by REFC delimiter
    …?ad_type=iframe&ad_size=728x90&section=1871072"></iframe></div></div><div clas…

    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 301, Column 224: reference to external entity in attribute value
    …?ad_type=iframe&ad_size=728x90&section=1871072"></iframe></div></div><div clas…

    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 301, Column 224: reference to entity "section" for which no system identifier could be generated
    …?ad_type=iframe&ad_size=728x90&section=1871072"></iframe></div></div><div clas…

    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 44, Column 180: entity was defined here
    …e.com/st?ad_type=iframe&ad_size=728x90&section=1845071"></iframe> <span style=…
  • Warning Line 303, Column 801: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?1285702&101"alt="traffic analysis"border="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.
  • Error Line 303, Column 849: end tag for "img" omitted, but OMITTAG NO was specified
    …traffic analysis"border="0"></noscript><script type="text/javascript" src="htt…

    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 303, Column 750: start tag was here
    …its()}catch(err){};</script><noscript><img src="http://sstatic1.histats.com/0.…

Visitor Analysis

Daily Visitor
  • 28.000 visits
Daily Visitor

In Page Analysis