wi-tribe.pk

wi-tribe, Pakistan's number 1 broadband company, is part of an international broadband service, bringing a new era of internet access. wi-tribe provides quality customer support and services to the consumers of Pakistan ...

Display Widget for this domain on your website. Click Here
This data was last updated from 15-02-2013 08:07:19  (update).

Overview Info

  • Domain Name
    wi-tribe.pk
  • Favicon
  • Alexa Rank
    #40288
  • Google Page Rank
    PR 4
  • Ip Address
    115.167.72.10
  • Page Size
    45.5 KB
  • Images
    0 GIF, 6 JPG, 10 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 1 0 0 1 0

Website Meta Analysis



  • Title
    wi-tribe | Pakistan’s No. 1 Broadband Company
  • Meta Keyword
    wireless broadband Pakistan, wireless broadband, Pakistan\'s number 1 broadband company, wireless broadband internet, wimax pakistan, wimax cpe pakistan, wimax technology pakistan, wireless internet pakistan, best internet service pakistan, mobile internet pakistan, fast speed internet pakistan, high quality wireless internet pakistan, wifi wimax pakistan, voip pakistan, wimax services, wimax islamabad, high speed internet, wireless internet pakistan, isp, wireless broadband, wireless communications pakistan, wireless broadband internet
  • Meta Description
    wi-tribe, Pakistan's number 1 broadband company, is part of an international broadband service, bringing a new era of internet access. wi-tribe provides quality customer support and services to the consumers of Pakistan

Technical Analysis



  • Webserver
    Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.8
  • Ip Address
    115.167.72.10
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from wi-tribe.pk.

HTML Analysis

  • date: Fri, 15 Feb 2013 08:08:01 GMT
  • server: Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 PHP/5.2.8
  • x-powered-by: PHP/5.2.8
  • x-pingback: http://www.wi-tribe.pk/xmlrpc.php
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for wi-tribe.pk

DNS Analysis


DNS servers
ns3.wi-tribe-nameservers.net [115.167.76.254]
ns2.wi-tribe-nameservers.net [115.167.73.254]
ns1.wi-tribe-nameservers.net [115.167.72.254]


DNS Records

Answer records
wi-tribe.pk SOA
server: ns1.wi-tribe-nameservers.net
email: hilal@afridi.pk.wi-tribe.com
serial: 2012061904
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 86400
86400s
wi-tribe.pk NS  ns2.wi-tribe-nameservers.net 86400s
wi-tribe.pk NS  ns3.wi-tribe-nameservers.net 86400s
wi-tribe.pk NS  ns4.wi-tribe-nameservers.net 86400s
wi-tribe.pk NS  ns5.wi-tribe-nameservers.net 86400s
wi-tribe.pk NS  ns6.wi-tribe-nameservers.net 86400s
wi-tribe.pk NS  ns1.wi-tribe-nameservers.net 86400s
wi-tribe.pk MX
preference: 0
exchange: pkedge01.wi-tribe.com
86400s
wi-tribe.pk MX
preference: 10
exchange: pkedge02.wi-tribe.com
86400s
wi-tribe.pk A 115.167.72.10 86400s

Authority records

Additional records
ns1.wi-tribe-nameservers.net A 115.167.72.254 86400s
ns2.wi-tribe-nameservers.net A 115.167.73.254 86400s
ns3.wi-tribe-nameservers.net A 115.167.76.254 86400s
ns4.wi-tribe-nameservers.net A 115.167.77.254 86400s
ns5.wi-tribe-nameservers.net A 115.167.74.254 86400s
ns6.wi-tribe-nameservers.net A 115.167.75.254 86400s
pkedge01.wi-tribe.com A 115.167.72.24 86400s
pkedge02.wi-tribe.com A 115.167.72.20 86400s

IP 115.167.72.10 Analysis

  • Country Code
    PK
  • Country Code3
    PAK
  • Country Name
    Pakistan
  • City
    Karachi
  • Continent Code
    AS
  • Latitude
    24.8667
  • Longitude
    67.05
  • % [whois.apnic.net node-6]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 115.167.72.0 - 115.167.72.255
    netname: WITRIBE
    descr: Telecom Services (DLI/WLL) Provider
    country: pk
    admin-c: MM714-AP
    tech-c: MM714-AP
    status: ASSIGNED NON-PORTABLE
    mnt-by: MAINT-PK-BURRAQTEL-ASADKARIM
    changed: asim.shehzad@pk.wi-tribe.net.pk 20091230
    changed: hm-changed@apnic.net 20100202
    source: APNIC

    route: 115.167.72.0/24
    descr: wi-tribe Route object1
    origin: AS38547
    country: PK
    notify: noman.jamil@pk.wi-tribe.com
    mnt-by: MAINT-PK-BURRAQTEL-ASADKARIM
    changed: noman.jamil@pk.wi-tribe.com 20090116
    changed: hm-changed@apnic.net 20090116
    source: APNIC

    person: Muhammad Sajid Malik
    nic-hdl: MM714-AP
    e-mail: sajid.malik919@gmail.com
    address: Plot 94-A, Street 7, Sector I-10/3
    address: Islamabad, Pakistan
    phone: +92-51-8250305
    fax-no: +92-51-4100856
    country: PK
    changed: noman.jamil@pk.wi-tribe.com 20101214
    mnt-by: MAINT-PK-BURRAQTEL-ASADKARIM
    changed: hm-changed@apnic.net 20111027
    source: APNIC


Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 42 Errors
  • 18 Warnings
Ratio Text/Html
  • 0.6436337901306054
Message Error
  • Error Line 19, Column 41: document type does not allow element "style" here
    		document.write('<style 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 20, Column 48: character "<" is the first character of a delimiter but occurred as data
    		document.write('div.domtab div{display:none;}<');

    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 22, Column 16: end tag for "style" omitted, but OMITTAG NO was specified
           </script>     

    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 19, Column 19: start tag was here
    		document.write('<style type="text/css">');    
  • Error Line 146, Column 142: required attribute "type" not specified
    …ugins/jquery-drop-down-menu-plugin/menu_style.css" type="text/css" /><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 151, Column 54: document type does not allow element "span" here
    	     //noCon("#dropmenu li:has(ul) a").append("<span>&nbsp;</span>"); 

    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 155, Column 58: document type does not allow element "span" here
    	     noCon("#dropmenu li ul li:has(ul) a").append("<span>&nbsp;</span>"); 

    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 158, Column 64: document type does not allow element "span" here
    …    noCon("#dropmenu li ul li ul li:has(ul) a").append("<span>&nbsp;</span>"); 

    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 162, Column 69: document type does not allow element "span" here
    …Con("#dropmenu li ul li ul li ul li:has(ul) a").append("<span>&nbsp;</span>"); 

    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 166, Column 76: document type does not allow element "span" here
    …dropmenu li ul li ul li ul li ul li:has(ul) a").append("<span>&nbsp;</span>"); 

    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 170, Column 82: document type does not allow element "span" here
    …nu li ul li ul li ul li ul li ul li:has(ul) a").append("<span>&nbsp;</span>"); 

    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 237, Column 68: document type does not allow element "div" here
    …ogle.maps.InfoWindow( {	content: "<div><font size='2' face='Verdana' color='#F…

    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 367, Column 14: end tag for "ul" which is not finished
    			      </ul>

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

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

  • Error Line 374, Column 158: required attribute "alt" not specified
    …//www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/oder-now-new.png" /></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 378, Column 166: required attribute "alt" not specified
    …://www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/pay-now-new.png" /></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>.

  • Warning Line 391, Column 403: cannot generate system identifier for general entity "ps_t"
    …e_pakistan/safe-textlink.js?ps_h=aWlb&ps_t="+new Date().getTime()+"&online-lin…

    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 391, Column 403: general entity "ps_t" not defined and no default entity
    …e_pakistan/safe-textlink.js?ps_h=aWlb&ps_t="+new Date().getTime()+"&online-lin…

    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 391, Column 407: reference not terminated by REFC delimiter
    …kistan/safe-textlink.js?ps_h=aWlb&ps_t="+new Date().getTime()+"&online-link-ht…

    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 391, Column 407: reference to entity "ps_t" for which no system identifier could be generated
    …kistan/safe-textlink.js?ps_h=aWlb&ps_t="+new Date().getTime()+"&online-link-ht…

    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 391, Column 402: entity was defined here
    …be_pakistan/safe-textlink.js?ps_h=aWlb&ps_t="+new Date().getTime()+"&online-li…
  • Warning Line 391, Column 433: cannot generate system identifier for general entity "online-link-html"
    …_h=aWlb&ps_t="+new Date().getTime()+"&online-link-html=Live%20Chat%20Online&of…

    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 391, Column 433: general entity "online-link-html" not defined and no default entity
    …_h=aWlb&ps_t="+new Date().getTime()+"&online-link-html=Live%20Chat%20Online&of…

    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 391, Column 449: reference not terminated by REFC delimiter
    …ew Date().getTime()+"&online-link-html=Live%20Chat%20Online&offline-link-html=…

    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 391, Column 449: reference to entity "online-link-html" for which no system identifier could be generated
    …ew Date().getTime()+"&online-link-html=Live%20Chat%20Online&offline-link-html=…

    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 391, Column 432: entity was defined here
    …s_h=aWlb&ps_t="+new Date().getTime()+"&online-link-html=Live%20Chat%20Online&o…
  • Warning Line 391, Column 471: cannot generate system identifier for general entity "offline-link-html"
    …online-link-html=Live%20Chat%20Online&offline-link-html=Live%20Chat%20Offline"…

    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 391, Column 471: general entity "offline-link-html" not defined and no default entity
    …online-link-html=Live%20Chat%20Online&offline-link-html=Live%20Chat%20Offline"…

    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 391, Column 488: reference not terminated by REFC delimiter
    …Live%20Chat%20Online&offline-link-html=Live%20Chat%20Offline";setTimeout("seaW…

    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 391, Column 488: reference to entity "offline-link-html" for which no system identifier could be generated
    …Live%20Chat%20Online&offline-link-html=Live%20Chat%20Offline";setTimeout("seaW…

    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 391, Column 470: entity was defined here
    …&online-link-html=Live%20Chat%20Online&offline-link-html=Live%20Chat%20Offline…
  • Error Line 420, Column 137: required attribute "alt" not specified
    …rc="http://wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/top_btn.png" /></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>.

  • Warning Line 422, Column 64: cannot generate system identifier for general entity "Component"
    …-tribe.pk/PInfranetServlet?page=login&Component=wtb.portal.web.ValidateUserBea…

    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 422, Column 64: general entity "Component" not defined and no default entity
    …-tribe.pk/PInfranetServlet?page=login&Component=wtb.portal.web.ValidateUserBea…

    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 422, Column 73: reference not terminated by REFC delimiter
    …/PInfranetServlet?page=login&Component=wtb.portal.web.ValidateUserBeanImpl&ses…

    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 422, Column 73: reference to external entity in attribute value
    …/PInfranetServlet?page=login&Component=wtb.portal.web.ValidateUserBeanImpl&ses…

    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 422, Column 73: reference to entity "Component" for which no system identifier could be generated
    …/PInfranetServlet?page=login&Component=wtb.portal.web.ValidateUserBeanImpl&ses…

    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 422, Column 63: entity was defined here
    …i-tribe.pk/PInfranetServlet?page=login&Component=wtb.portal.web.ValidateUserBe…
  • Warning Line 422, Column 110: cannot generate system identifier for general entity "sessionState"
    …t=wtb.portal.web.ValidateUserBeanImpl&sessionState=start">The all-new my wi-tr…

    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 422, Column 110: general entity "sessionState" not defined and no default entity
    …t=wtb.portal.web.ValidateUserBeanImpl&sessionState=start">The all-new my wi-tr…

    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 422, Column 122: reference not terminated by REFC delimiter
    …l.web.ValidateUserBeanImpl&sessionState=start">The all-new my wi-tribe</a></li>

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

  • Warning Line 422, Column 122: reference to external entity in attribute value
    …l.web.ValidateUserBeanImpl&sessionState=start">The all-new my wi-tribe</a></li>

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

  • Error Line 422, Column 122: reference to entity "sessionState" for which no system identifier could be generated
    …l.web.ValidateUserBeanImpl&sessionState=start">The all-new my wi-tribe</a></li>

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

  • Info Line 422, Column 109: entity was defined here
    …nt=wtb.portal.web.ValidateUserBeanImpl&sessionState=start">The all-new my wi-t…
  • Error Line 444, Column 87: required attribute "alt" not specified
    …="http://www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/share_btn.png" />

    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 453, Column 234: required attribute "alt" not specified
    …c="http://www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/fbook.png"/></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 457, Column 212: required attribute "alt" not specified
    …http://www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/twitter.png" /></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 459, Column 228: required attribute "alt" not specified
    …http://www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/youtube.png" /></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 462, Column 185: required attribute "alt" not specified
    …rc="http://www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/rss.png" /></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 534, Column 58: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    …sp;&nbsp;&nbsp;&nbsp;&nbsp;<font face:"arial" color="#FF0000">Please enable ja…

    Have you forgotten the "equal" sign marking the separation between the attribute and its declared value? Typical syntax is attribute="value".

  • Warning Line 572, Column 69: reference not terminated by REFC delimiter
    …/PInfranetServlet?page=login&Component=wtb.portal.web.ValidateUserBeanImpl&ses…

    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 572, Column 69: reference to external entity in attribute value
    …/PInfranetServlet?page=login&Component=wtb.portal.web.ValidateUserBeanImpl&ses…

    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 572, Column 69: reference to entity "Component" for which no system identifier could be generated
    …/PInfranetServlet?page=login&Component=wtb.portal.web.ValidateUserBeanImpl&ses…

    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 422, Column 63: entity was defined here
    …i-tribe.pk/PInfranetServlet?page=login&Component=wtb.portal.web.ValidateUserBe…
  • Warning Line 572, Column 118: reference not terminated by REFC delimiter
    ….web.ValidateUserBeanImpl&sessionState=start"><img src="http://www.wi-tribe.pk…

    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 572, Column 118: reference to external entity in attribute value
    ….web.ValidateUserBeanImpl&sessionState=start"><img src="http://www.wi-tribe.pk…

    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 572, Column 118: reference to entity "sessionState" for which no system identifier could be generated
    ….web.ValidateUserBeanImpl&sessionState=start"><img src="http://www.wi-tribe.pk…

    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 422, Column 109: entity was defined here
    …nt=wtb.portal.web.ValidateUserBeanImpl&sessionState=start">The all-new my wi-t…
  • Error Line 574, Column 44: ID "slidebanner" already defined
    </dd><dt>Perfect Packages</dt><dd><div id="slidebanner">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 571, Column 181: ID "slidebanner" first defined here
    …th:98%;height:300px"><dt>The all-new my wi-tribe</dt><dd><div id="slidebanner">
  • Error Line 577, Column 55: ID "slidebanner" already defined
    </dd><dt>Win a Wi-Fi Digital Camera!</dt><dd><div id="slidebanner">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 571, Column 181: ID "slidebanner" first defined here
    …th:98%;height:300px"><dt>The all-new my wi-tribe</dt><dd><div id="slidebanner">
  • Error Line 580, Column 50: ID "slidebanner" already defined
    </dd><dt>New Unlimited Packages</dt><dd><div id="slidebanner">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 571, Column 181: ID "slidebanner" first defined here
    …th:98%;height:300px"><dt>The all-new my wi-tribe</dt><dd><div id="slidebanner">
  • Error Line 581, Column 230: required attribute "alt" not specified
    …ner-unlimited.jpg" width="840" class="alignnone size-full wp-image-3928" /></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 592, Column 86: required attribute "alt" not specified
    …ttp://www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/banner_1.jpg" /></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>.

  • Warning Line 595, Column 52: character "&" is the first character of a delimiter but occurred as data
    …low" title="Enjoy our latest packages & promos" href="http://www.wi-tribe.pk/p…

    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 596, Column 86: required attribute "alt" not specified
    …ttp://www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/banner_2.jpg" /></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 600, Column 86: required attribute "alt" not specified
    …ttp://www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/banner_3.jpg" /></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 607, Column 87: required attribute "alt" not specified
    …www.wi-tribe.pk/wp-content/themes/wi-tribe-pk/images/banner_4.jpg" /></a></div>

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

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

  • Error Line 771, Column 13: end tag for element "div" which is not open
    </html></div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 774, Column 6: end tag for element "div" which is not open
    </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

Visitor Analysis

Daily Visitor
  • 4.433 visits
Daily Visitor

In Page Analysis