unblockyoutube.us

unblockyoutube.us has Alexa Rank 17.037 and Google Page Rank is 0

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

Overview Info

  • Domain Name
    unblockyoutube.us
  • Favicon
  • Alexa Rank
    #17037
  • Google Page Rank
    PR 0
  • Ip Address
    208.53.158.137
  • Page Size
    6.1 KB
  • Images
    1 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 0 0 0 0 0

Website Meta Analysis



  • Title
    Unblock YouTube | Free & Compatible YouTube Unblocker
  • Meta Keyword
    unblock, youtube, unblock youtube, unblocker

Technical Analysis



  • Webserver
    Apache/2.2.15 (CentOS)
  • Ip Address
    208.53.158.137
  • Domain Age
    4 Years, 0 Months, 26 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from unblockyoutube.us.

HTML Analysis

  • date: Fri, 06 Sep 2013 18:10:44 GMT
  • server: Apache/2.2.15 (CentOS)
  • x-powered-by: PHP/5.3.3
  • cache-control: no-store, no-cache, must-revalidate
  • last-modified: Fri, 25 Jan 2013 01:50:53 GMT
  • pragma: no-cache
  • content-length: 6678
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: UNBLOCKYOUTUBE.US
Domain ID: D22068709-US
Sponsoring Registrar: ENOM, INC.
Registrar URL (registration services): whois.enom.com
Domain Status: ok
Registrant ID: CR18158700
Registrant Name: Nicholas Webster
Registrant Address1: 12 Barlea Avenue
Registrant City: Manchester
Registrant State/Province: Lancashire
Registrant Postal Code: M40 3WL
Registrant Country: United Kingdom
Registrant Country Code: UK
Registrant Phone Number: +7.894992029
Registrant Email: email
Registrant Application Purpose: P3
Registrant Nexus Category: C11
Administrative Contact ID: CR18158702
Administrative Contact Name: Nicholas Webster
Administrative Contact Address1: 12 Barlea Avenue
Administrative Contact City: Manchester
Administrative Contact State/Province: Lancashire
Administrative Contact Postal Code: M40 3WL
Administrative Contact Country: United Kingdom
Administrative Contact Country Code: UK
Administrative Contact Phone Number: +7.894992029
Administrative Contact Email: email
Administrative Application Purpose: P3
Administrative Nexus Category: C11
Billing Contact ID: CR18158703
Billing Contact Name: Nicholas Webster
Billing Contact Address1: 12 Barlea Avenue
Billing Contact City: Manchester
Billing Contact State/Province: Lancashire
Billing Contact Postal Code: M40 3WL
Billing Contact Country: United Kingdom
Billing Contact Country Code: UK
Billing Contact Phone Number: +7.894992029
Billing Contact Email: email
Billing Application Purpose: P3
Billing Nexus Category: C11
Technical Contact ID: CR18158701
Technical Contact Name: Nicholas Webster
Technical Contact Address1: 12 Barlea Avenue
Technical Contact City: Manchester
Technical Contact State/Province: Lancashire
Technical Contact Postal Code: M40 3WL
Technical Contact Country: United Kingdom
Technical Contact Country Code: UK
Technical Contact Phone Number: +7.894992029
Technical Contact Email: email
Technical Application Purpose: P3
Technical Nexus Category: C11
Name Server: NS1.DNEASY.NET
Name Server: NS2.DNEASY.NET
Name Server: NS3.DNEASY.NET
Name Server: NS4.DNEASY.NET
Created by Registrar: GODADDY.COM, INC.
Last Updated by Registrar: ENOM, INC.
Last Transferred Date: Sun Jul 31 18:35:54 GMT 2011
Domain Registration Date: Tue Sep 01 16:08:54 GMT 2009
Domain Expiration Date: Sat Aug 31 23:59:59 GMT 2013
Domain Last Updated Date: Thu Aug 09 13:09:36 GMT 2012

>>>> Whois database was last updated on: Tue Feb 05 09:25:48 GMT 2013

DNS Analysis


DNS servers
ns4.dneasy.net
ns3.dneasy.net
ns1.dneasy.net
ns2.dneasy.net


DNS Records

Answer records
unblockyoutube.us NS  ns1.dneasy.net 172800s
unblockyoutube.us A 76.73.44.59 3600s
unblockyoutube.us NS  ns4.dneasy.net 172800s
unblockyoutube.us NS  ns3.dneasy.net 172800s
unblockyoutube.us A 174.36.81.33 3600s
unblockyoutube.us NS  ns2.dneasy.net 172800s
unblockyoutube.us SOA
server: ns1.dneasy.net
email: unbannernetwork@gmail.com
serial: 2013013101
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 38400
172800s
unblockyoutube.us A 206.217.194.25 3600s
unblockyoutube.us A 198.105.216.190 3600s
unblockyoutube.us A 208.53.158.137 3600s

Authority records

Additional records
ns4.dneasy.net A 69.85.93.117 172800s
ns2.dneasy.net 28 [16 bytes] 172800s
ns3.dneasy.net 28 [16 bytes] 172800s
ns1.dneasy.net A 50.31.1.17 172800s
ns3.dneasy.net A 106.187.48.223 172800s
ns2.dneasy.net A 95.211.165.80 172800s
ns4.dneasy.net 28 [16 bytes] 172800s
ns1.dneasy.net 28 [16 bytes] 172800s

IP 208.53.158.137 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Bronx
  • Continent Code
    718
  • Latitude
    501
  • Longitude
    501
  • %rwhois V-1.5:003eff:00 rwhois.fdcservers.net (by Network Solutions, Inc. V-1.5.10-pre6)
    network:Auth-Area:208.53.128.0/18
    network:Class-Name:network
    network:OrgName:Zenex 5ive Limited
    network:OrgID;I:FDC-1013
    network:Address:5 Jupiter House, Calleva Park
    network:City:Aldermaston, Reading
    network:PostalCode:RG7 8NN
    network:Country:GB
    network:NetRange:208.53.158.137 - 208.53.158.137
    network:CIDR:208.53.158.137/32
    network:NetName:FDC-1013-208.53.158.137
    network:OrgAbuseHandle:ABUSE438-ARIN
    network:OrgAbuseName:Abuse Department
    network:OrgAbusePhone:+1-312-423-6675
    network:OrgAbuseEmail:abuse@fdcservers.net
    network:OrgNOCHandle:TECHS72-ARIN
    network:OrgNOCName:Tech Support
    network:OrgNOCPhone:+1-312-423-6675
    network:OrgNOCEmail:support@fdcservers.net
    network:OrgTechHandle:TECHS72-ARIN
    network:OrgTechName:Tech Support
    network:OrgTechPhone:+1-312-423-6675
    network:OrgTechEmail:support@fdcservers.net

    %ok

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 36 Errors
  • 14 Warnings
Ratio Text/Html
  • 0.5837067861715749
Message Error
  • Error Line 44, Column 21: there is no attribute "FRAMEBORDER"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…

    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 44, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…
  • Error Line 44, Column 35: there is no attribute "MARGINWIDTH"
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…

    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 44, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGH…
  • Error Line 44, Column 50: there is no attribute "MARGINHEIGHT"
    …MEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="…

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

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

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

  • Error Line 44, Column 50: 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 62: there is no attribute "SCROLLING"
    …ARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://ad.yi…

    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 44, Column 62: 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://ad.yi…
  • Error Line 44, Column 71: there is no attribute "WIDTH"
    …H=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://ad.yieldmanage…

    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 44, Column 71: 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://ad.yieldmanage…
  • Error Line 44, Column 82: there is no attribute "HEIGHT"
    …EIGHT=0 SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://ad.yieldmanager.com/st?ad…

    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 44, Column 82: 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://ad.yieldmanager.com/st?ad…
  • Error Line 44, Column 89: there is no attribute "SRC"
    … SCROLLING=NO WIDTH=728 HEIGHT=90 SRC="http://ad.yieldmanager.com/st?ad_type=i…

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

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

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

  • Warning Line 44, Column 135: cannot generate system identifier for general entity "ad_size"
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></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 135: general entity "ad_size" not defined and no default entity
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></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 142: reference not terminated by REFC delimiter
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAME>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 44, Column 142: reference to external entity in attribute value
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAME>

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

  • Error Line 44, Column 142: reference to entity "ad_size" for which no system identifier could be generated
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAME>

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

  • Info Line 44, Column 134: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAM…
  • Warning Line 44, Column 150: cannot generate system identifier for general entity "section"
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></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 150: general entity "section" not defined and no default entity
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></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 157: reference not terminated by REFC delimiter
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAME>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 44, Column 157: reference to external entity in attribute value
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAME>

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

  • Error Line 44, Column 157: reference to entity "section" for which no system identifier could be generated
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAME>

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

  • Info Line 44, Column 149: entity was defined here
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAME>
  • Error Line 44, Column 166: element "IFRAME" undefined
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAME>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 61, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 61, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 61, Column 50: 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 61, Column 62: 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://ad.y…
  • Error Line 61, Column 71: 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://ad.yieldmanag…
  • Error Line 61, Column 82: 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://ad.yieldmanager.com/st?a…
  • Warning Line 61, Column 143: reference not terminated by REFC delimiter
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 61, Column 143: reference to external entity in attribute value
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

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

  • Error Line 61, Column 143: reference to entity "ad_size" for which no system identifier could be generated
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

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

  • Info Line 44, Column 134: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAM…
  • Warning Line 61, Column 159: reference not terminated by REFC delimiter
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 61, Column 159: reference to external entity in attribute value
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

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

  • Error Line 61, Column 159: reference to entity "section" for which no system identifier could be generated
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

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

  • Info Line 44, Column 149: entity was defined here
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAME>
  • Error Line 61, Column 168: element "IFRAME" undefined
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 67, Column 21: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 67, Column 35: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <IFRAME FRAMEBORDER=0 MARGINWIDTH=0 MARGINHEIGHT=0 SCROLLING=NO WIDTH=300 HEIGH…
  • Error Line 67, Column 50: 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 67, Column 62: 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://ad.y…
  • Error Line 67, Column 71: 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://ad.yieldmanag…
  • Error Line 67, Column 82: 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://ad.yieldmanager.com/st?a…
  • Warning Line 67, Column 143: reference not terminated by REFC delimiter
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 67, Column 143: reference to external entity in attribute value
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

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

  • Error Line 67, Column 143: reference to entity "ad_size" for which no system identifier could be generated
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

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

  • Info Line 44, Column 134: entity was defined here
    …/ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAM…
  • Warning Line 67, Column 159: reference not terminated by REFC delimiter
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 67, Column 159: reference to external entity in attribute value
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

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

  • Error Line 67, Column 159: reference to entity "section" for which no system identifier could be generated
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

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

  • Info Line 44, Column 149: entity was defined here
    …ad.yieldmanager.com/st?ad_type=iframe&ad_size=728x90&section=3929820"></IFRAME>
  • Error Line 67, Column 168: element "IFRAME" undefined
    …d.yieldmanager.com/st?ad_type=iframe&ad_size=300x250&section=3929820"></IFRAME>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).

Visitor Analysis

Daily Visitor
  • 12.600 visits

In Page Analysis