reciente ...

sep.gob.mx
  • Domain Name
    sep.gob.mx
  • Favicon
  • Google Page Rank
    8
  • Alexa Rank
    #12177
  • Page Size
    46.6 KB
  • Ip Address
    168.255.254.59
  • Heading
    H1: 1, H2: 8, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    3 GIF, 28 JPG, 6 PNG

Website Meta Analysis

  • Title
    Secretaría de Educación Pública :: Inicio
  • Meta Keyword
    Secretario de Educación Pública,Historia de la SEP,Secretaría de Educación Pública,Becas,Estadísticas,Históricas,Nacionales,Bibliotecas,Escuela,Red Escolar,Organismos Desconcentrados, Sector Paraestatal,Desconcentrados,Derechos de Autor,Educación por niveles,Educación Inicial,La SEP para los niños,Educación Media Superior, Educación Superior
  • Meta Description
    reciente

Technical Analysis

  • Webserver
    Sun GlassFish Enterprise Server v2.1.1
  • Ip Address
    168.255.254.59
  • Domain Age
  • Javascript Library
    dojo
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from sep.gob.mx.

HTML Analysis

  • x-powered-by: Servlet/2.5
  • server: Sun GlassFish Enterprise Server v2.1.1
  • p3p: policyref="/w3c/p3p.xml"
  • cache-control: no-cache
  • pragma: no-cache
  • content-encoding: gzip
  • content-type: text/html
  • date: Fri, 22 Feb 2013 01:57:34 GMT
  • x-cache: MISS from SEP
  • x-cache-lookup: MISS from SEP:80
  • via: 1.0 SEP (squid)
  • connection: close
  • x-google-cache-control: remote-fetch

Domain Name: sep.gob.mx

Created On: 1995-01-01
Expiration Date: 2012-12-31
Last Updated On: 2012-01-01
Registrar: Akky (Una division de NIC Mexico)
URL: http://www.akky.mx
Whois TCP URI: whois.akky.mx
Whois Web URL: http://www.akky.mx/jsf/whois/whois.jsf

Registrant:
Name: Secretaria de Educacion Publica
City: Mexico
State: Distrito Federal
Country: Mexico

Administrative Contact:
Name: Luis Jorge Tejada Figueroa
City: Mexico
State: Distrito Federal
Country: Mexico

Technical Contact:
Name: Luis Jorge Tejada Figueroa
City: Mexico
State: Distrito Federal
Country: Mexico

Billing Contact:
Name: Luis Jorge Tejada Figueroa
City: Mexico
State: Distrito Federal
Country: Mexico

Name Servers:
DNS: dns1.sep.gob.mx 168.255.253.11
DNS: dns2.sep.gob.mx 168.255.253.12


% NOTICE: The expiration date displayed in this record is the date the
% registrar's sponsorship of the domain name registration in the registry is
% currently set to expire. This date does not necessarily reflect the
% expiration date of the domain name registrant's agreement with the sponsoring
% registrar. Users may consult the sponsoring registrar's Whois database to
% view the registrar's reported date of expiration for this registration.

% The requested information ("Information") is provided only for the delegation
% of domain names and the operation of the DNS administered by NIC Mexico.

% It is absolutely prohibited to use the Information for other purposes,
% including sending not requested emails for advertising or promoting products
% and services purposes (SPAM) without the authorization of the owners of the
% Information and NIC Mexico.

% The database generated from the delegation system is protected by the
% intellectual property laws and all international treaties on the matter.

% If you need more information on the records displayed here, please contact us
% by email at email .

% If you want notify the receipt of SPAM or unauthorized access, please send a
% email to email .

% NOTA: La fecha de expiracion mostrada en esta consulta es la fecha que el
% registrar tiene contratada para el nombre de dominio en el registry. Esta
% fecha no necesariamente refleja la fecha de expiracion del nombre de dominio
% que el registrante tiene contratada con el registrar. Puede consultar la base
% de datos de Whois del registrar para ver la fecha de expiracion reportada por
% el registrar para este nombre de dominio.

% La informacion que ha solicitado se provee exclusivamente para fines
% relacionados con la delegacion de nombres de dominio y la operacion del DNS
% administrado por NIC Mexico.

% Queda absolutamente prohibido su uso para otros propositos, incluyendo el
% envio de Correos Electronicos no solicitados con fines publicitarios o de
% promocion de productos y servicios (SPAM) sin mediar la autorizacion de los
% afectados y de NIC Mexico.

% La base de datos generada a partir del sistema de delegacion, esta protegida
% por las leyes de Propiedad Intelectual y todos los tratados internacionales
% sobre la materia.

% Si necesita mayor informacion sobre los registros aqui mostrados, favor de
% comunicarse a email .

% Si desea notificar sobre correo no solicitado o accesos no autorizados, favor
% de enviar su mensaje a email .

DNS Analysis


DNS servers
dns2.sep.gob.mx [168.255.253.12]
dns1.sep.gob.mx [168.255.253.11]


DNS Records

Answer records
sep.gob.mx A 168.255.254.59 300s
sep.gob.mx MX
preference: 10
exchange: as2.sep.gob.mx
300s
sep.gob.mx MX
preference: 10
exchange: as.sep.gob.mx
300s
sep.gob.mx SOA
server: dns1.sep.gob.mx
email: dns@sep.gob.mx
serial: 159
refresh: 10800
retry: 3600
expire: 2419200
minimum ttl: 300
300s
sep.gob.mx TXT v=spf1 ip4:168.255.253.234 ip4:168.255.253.252 300s
sep.gob.mx NS  dns2.sep.gob.mx 300s
sep.gob.mx NS  dns1.sep.gob.mx 300s

Authority records

Additional records
as2.sep.gob.mx A 168.255.253.234 300s
as.sep.gob.mx A 168.255.253.252 300s
dns2.sep.gob.mx A 168.255.253.12 300s
dns1.sep.gob.mx A 168.255.253.11 300s

IP 168.255.254.59 Analysis

  • Country Code
    MX
  • Country Code3
    MEX
  • Country Name
    Mexico
  • City
    Mexico
  • Continent Code
    NA
  • Latitude
    19.4342
  • Longitude
    99.1386

  • % Joint Whois - whois.lacnic.net
    % This server accepts single ASN, IPv4 or IPv6 queries

    % LACNIC resource: whois.lacnic.net


    % Copyright LACNIC lacnic.net
    % The data below is provided for information purposes
    % and to assist persons in obtaining information about or
    % related to AS and IP numbers registrations
    % By submitting a whois query, you agree to use this data
    % only for lawful purposes.
    % 2013-01-24 20:42:08 (BRST -02:00)

    inetnum: 168.255/16
    status: assigned
    aut-num: N/A
    owner: Secretaria de Educacion Publica
    ownerid: MX-SEPU-LACNIC
    responsible: Gloria Liliana Luna Fandi�o
    address: Viaducto Col. Madalena Mixiuhca, 551,
    address: 15900 - M�xico - DF
    country: MX
    phone: +52 55 36017215 []
    owner-c: GLF3
    tech-c: GLF3
    inetrev: 168.255/16
    nserver: DNS1.SEP.GOB.MX
    nsstat: 20130119 AA
    nslastaa: 20130119
    nserver: DNS2.SEP.GOB.MX
    nsstat: 20130119 AA
    nslastaa: 20130119
    created: 19941025
    changed: 19980720

    nic-hdl: GLF3
    person: Marco Antonio San Juan Rivera
    e-mail: marco@SEP.GOB.MX
    address: Viaducto Col. Madalena Mixiuhca, 551, Magdalena Mixihuca
    address: 15900 - M�xico - DF
    country: MX
    phone: +52 5536013315 []
    created: 20080619
    changed: 20121127

    % whois.lacnic.net accepts only direct match queries.
    % Types of queries are: POCs, ownerid, CIDR blocks, IP
    % and AS numbers.

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 24 Errors
  • 29 Warnings
Ratio Text/Html
  • 0.649588960657663
Message Error
  • Warning Line 101, Column 109: cannot generate system identifier for general entity "_idDependencia"
    …/pot/directorio/begin.do?method=begin&_idDependencia=11">Directorio SEP </a></…

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

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

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

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

  • Error Line 101, Column 109: general entity "_idDependencia" not defined and no default entity
    …/pot/directorio/begin.do?method=begin&_idDependencia=11">Directorio SEP </a></…

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

  • Warning Line 101, Column 123: reference not terminated by REFC delimiter
    …ot/directorio/begin.do?method=begin&_idDependencia=11">Directorio SEP </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 101, Column 123: reference to external entity in attribute value
    …ot/directorio/begin.do?method=begin&_idDependencia=11">Directorio SEP </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 101, Column 123: reference to entity "_idDependencia" for which no system identifier could be generated
    …ot/directorio/begin.do?method=begin&_idDependencia=11">Directorio SEP </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 101, Column 108: entity was defined here
    …x/pot/directorio/begin.do?method=begin&_idDependencia=11">Directorio SEP </a><…
  • Warning Line 387, Column 111: cannot generate system identifier for general entity "redireccionado"
    …encia/showDependencia.do?method=begin&redireccionado=true&_idDependencia=11" o…

    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 387, Column 111: general entity "redireccionado" not defined and no default entity
    …encia/showDependencia.do?method=begin&redireccionado=true&_idDependencia=11" o…

    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 387, Column 125: reference not terminated by REFC delimiter
    …ndencia.do?method=begin&redireccionado=true&_idDependencia=11" onclick="window…

    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 387, Column 125: reference to external entity in attribute value
    …ndencia.do?method=begin&redireccionado=true&_idDependencia=11" onclick="window…

    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 387, Column 125: reference to entity "redireccionado" for which no system identifier could be generated
    …ndencia.do?method=begin&redireccionado=true&_idDependencia=11" onclick="window…

    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 387, Column 110: entity was defined here
    …dencia/showDependencia.do?method=begin&redireccionado=true&_idDependencia=11" …
  • Warning Line 387, Column 145: reference not terminated by REFC delimiter
    …gin&redireccionado=true&_idDependencia=11" onclick="window.location.href='/es/…

    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 387, Column 145: reference to external entity in attribute value
    …gin&redireccionado=true&_idDependencia=11" onclick="window.location.href='/es/…

    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 387, Column 145: reference to entity "_idDependencia" for which no system identifier could be generated
    …gin&redireccionado=true&_idDependencia=11" onclick="window.location.href='/es/…

    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 101, Column 108: entity was defined here
    …x/pot/directorio/begin.do?method=begin&_idDependencia=11">Directorio SEP </a><…
  • Warning Line 422, Column 155: cannot generate system identifier for general entity "view"
    …p.gob.mx/index.php?option=com_content&view=article&id=113&Itemid=90">      <im…

    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 155: general entity "view" not defined and no default entity
    …p.gob.mx/index.php?option=com_content&view=article&id=113&Itemid=90">      <im…

    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 159: reference not terminated by REFC delimiter
    …b.mx/index.php?option=com_content&view=article&id=113&Itemid=90">      <img sr…

    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 159: reference to external entity in attribute value
    …b.mx/index.php?option=com_content&view=article&id=113&Itemid=90">      <img sr…

    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 159: reference to entity "view" for which no system identifier could be generated
    …b.mx/index.php?option=com_content&view=article&id=113&Itemid=90">      <img sr…

    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 154: entity was defined here
    …ep.gob.mx/index.php?option=com_content&view=article&id=113&Itemid=90">      <i…
  • Warning Line 422, Column 168: cannot generate system identifier for general entity "id"
    …x.php?option=com_content&view=article&id=113&Itemid=90">      <img src="/work/…

    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 168: general entity "id" not defined and no default entity
    …x.php?option=com_content&view=article&id=113&Itemid=90">      <img src="/work/…

    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 170: reference not terminated by REFC delimiter
    …php?option=com_content&view=article&id=113&Itemid=90">      <img src="/work/mo…

    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 170: reference to external entity in attribute value
    …php?option=com_content&view=article&id=113&Itemid=90">      <img src="/work/mo…

    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 170: reference to entity "id" for which no system identifier could be generated
    …php?option=com_content&view=article&id=113&Itemid=90">      <img src="/work/mo…

    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 167: entity was defined here
    …ex.php?option=com_content&view=article&id=113&Itemid=90">      <img src="/work…
  • Warning Line 422, Column 175: cannot generate system identifier for general entity "Itemid"
    …ption=com_content&view=article&id=113&Itemid=90">      <img src="/work/models/…

    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 175: general entity "Itemid" not defined and no default entity
    …ption=com_content&view=article&id=113&Itemid=90">      <img src="/work/models/…

    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 181: reference not terminated by REFC delimiter
    …com_content&view=article&id=113&Itemid=90">      <img src="/work/models/sep1/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 422, Column 181: reference to external entity in attribute value
    …com_content&view=article&id=113&Itemid=90">      <img src="/work/models/sep1/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 422, Column 181: reference to entity "Itemid" for which no system identifier could be generated
    …com_content&view=article&id=113&Itemid=90">      <img src="/work/models/sep1/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 422, Column 174: entity was defined here
    …option=com_content&view=article&id=113&Itemid=90">      <img src="/work/models…
  • Warning Line 422, Column 527: reference not terminated by REFC delimiter
    …b.mx/index.php?option=com_content&view=article&id=113&Itemid=90">Equidad de gé…

    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 527: reference to external entity in attribute value
    …b.mx/index.php?option=com_content&view=article&id=113&Itemid=90">Equidad de gé…

    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 527: reference to entity "view" for which no system identifier could be generated
    …b.mx/index.php?option=com_content&view=article&id=113&Itemid=90">Equidad de gé…

    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 154: entity was defined here
    …ep.gob.mx/index.php?option=com_content&view=article&id=113&Itemid=90">      <i…
  • Warning Line 422, Column 538: reference not terminated by REFC delimiter
    …php?option=com_content&view=article&id=113&Itemid=90">Equidad de género</a></p…

    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 538: reference to external entity in attribute value
    …php?option=com_content&view=article&id=113&Itemid=90">Equidad de género</a></p…

    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 538: reference to entity "id" for which no system identifier could be generated
    …php?option=com_content&view=article&id=113&Itemid=90">Equidad de género</a></p…

    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 167: entity was defined here
    …ex.php?option=com_content&view=article&id=113&Itemid=90">      <img src="/work…
  • Warning Line 422, Column 549: reference not terminated by REFC delimiter
    …com_content&view=article&id=113&Itemid=90">Equidad de género</a></p>    <p>&nb…

    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 549: reference to external entity in attribute value
    …com_content&view=article&id=113&Itemid=90">Equidad de género</a></p>    <p>&nb…

    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 549: reference to entity "Itemid" for which no system identifier could be generated
    …com_content&view=article&id=113&Itemid=90">Equidad de género</a></p>    <p>&nb…

    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 174: entity was defined here
    …option=com_content&view=article&id=113&Itemid=90">      <img src="/work/models…
  • Warning Line 422, Column 694: reference not terminated by REFC delimiter
    …b.mx/index.php?option=com_content&view=article&id=113&Itemid=90">en la SEP</a>…

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

  • Warning Line 422, Column 694: reference to external entity in attribute value
    …b.mx/index.php?option=com_content&view=article&id=113&Itemid=90">en la SEP</a>…

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

  • Error Line 422, Column 694: reference to entity "view" for which no system identifier could be generated
    …b.mx/index.php?option=com_content&view=article&id=113&Itemid=90">en la SEP</a>…

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

  • Info Line 422, Column 154: entity was defined here
    …ep.gob.mx/index.php?option=com_content&view=article&id=113&Itemid=90">      <i…
  • Warning Line 422, Column 705: reference not terminated by REFC delimiter
    …php?option=com_content&view=article&id=113&Itemid=90">en la SEP</a></p>  </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 422, Column 705: reference to external entity in attribute value
    …php?option=com_content&view=article&id=113&Itemid=90">en la SEP</a></p>  </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 422, Column 705: reference to entity "id" for which no system identifier could be generated
    …php?option=com_content&view=article&id=113&Itemid=90">en la SEP</a></p>  </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 422, Column 167: entity was defined here
    …ex.php?option=com_content&view=article&id=113&Itemid=90">      <img src="/work…
  • Warning Line 422, Column 716: reference not terminated by REFC delimiter
    …com_content&view=article&id=113&Itemid=90">en la SEP</a></p>  </div></div><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 422, Column 716: reference to external entity in attribute value
    …com_content&view=article&id=113&Itemid=90">en la SEP</a></p>  </div></div><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 422, Column 716: reference to entity "Itemid" for which no system identifier could be generated
    …com_content&view=article&id=113&Itemid=90">en la SEP</a></p>  </div></div><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 422, Column 174: entity was defined here
    …option=com_content&view=article&id=113&Itemid=90">      <img src="/work/models…
  • Error Line 495, Column 203: required attribute "alt" not specified
    …ight="31" style="margin-right: 6px;" /></a> <a href="http://twitter.com/SEP_mx…

    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 495, Column 337: required attribute "alt" not specified
    …ight="31" style="margin-right: 6px;" /></a> <a href="http://www.youtube.com/ca…

    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 495, Column 477: required attribute "alt" not specified
    …ight="31" style="margin-right: 6px;" /></a> <a href="http://www.sep.gob.mx/swb…

    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 495, Column 598: required attribute "alt" not specified
    …"><img src="/work/models/sep1/css/rs2.png" width="31" height="31" /></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 500, Column 117: required attribute "alt" not specified
    …go_footer.png" style="float:left; margin: 0px 24px;" width="220" height="70" />

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

  • Error Line 606, Column 41: there is no attribute "language"
    …cript type="text/javascript" language="javascript" src="/work/models/sep1/js/g…

    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.

Visitor Analysis

Daily Visitor
  • 15.633 visits
Daily Visitor