Online Recharge - Online Prepaid Mobile, DTH and DataCard Recharge and Top Up Services. Recharge all Prepaid Mobile, Dth and DataCards with India's most secure Online Recharge and Top up service provider company. ...

paytm.com
  • Domain Name
    paytm.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #2643
  • Page Size
    32.5 KB
  • Ip Address
    46.137.222.6
  • Heading
    H1: 0, H2: 0, H3: 1, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    Online Recharge - Online Prepaid Mobile, DTH and DataCard Recharge for Airtel, Vodafone, Reliance, BSNL, Idea, Uninor, MTS, Tata Docomo, Tata Indicom, MTNL, Loop Mobile, Cheers, Ping, S Tel
  • Meta Keyword
  • Meta Description
    Online Recharge - Online Prepaid Mobile, DTH and DataCard Recharge and Top Up Services. Recharge all Prepaid Mobile, Dth and DataCards with India's most secure Online Recharge and Top up service provider company. Paytm offers online recharge for Airtel, Vodafone, Reliance, Idea, Tata Indicom & Docomo, Tata Sky, Dish TV, Tata Photon and all mobile, dth and datacard operator across India.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    46.137.222.6
  • Domain Age
    10 Years, 2 Months, 13 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from paytm.com.

HTML Analysis

  • server: nginx
  • date: Wed, 11 Sep 2013 11:55:46 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: Express
  • etag: "1158216489"
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
PayTM Mobile Solutions Pvt Ltd
B-121, Sector 5
Noida, Uttar Pradesh 201301
India

Domain Name: PAYTM.COM
Created on: 23-Jun-03
Expires on: 23-Jun-20
Last Updated on: 30-Jul-12

Administrative Contact:
Shekhar Sharma, Vijay email
PayTM Mobile Solutions Pvt Ltd
B-121, Sector 5
Noida, Uttar Pradesh 201301
India
+91.0114770770

Technical Contact:
Shekhar Sharma, Vijay email
PayTM Mobile Solutions Pvt Ltd
B-121, Sector 5
Noida, Uttar Pradesh 201301
India
+91.0114770770

Domain servers in listed order:
NS1.P15.DYNECT.NET
NS2.P15.DYNECT.NET
NS3.P15.DYNECT.NET
NS4.P15.DYNECT.NET

DNS Analysis


DNS servers
ns-249.awsdns-31.com [205.251.192.249]
ns-998.awsdns-60.net
ns-1112.awsdns-11.org
ns-1858.awsdns-40.co.uk

DNS Records

Answer records

Authority records

Additional records

IP 46.137.222.6 Analysis

  • Country Code
    DE
  • Country Code3
    DEU
  • Country Name
    Germany
  • City
    EU
  • Continent Code
    51° North
  • Latitude
    9.
  • Longitude
  • No whois ip data for 46.137.222.6

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 59 Errors
  • 16 Warnings
Ratio Text/Html
  • 0.7364406270646886
Message Error
  • Error Line 6, Column 18: document type does not allow element "noscript" here; assuming missing "object" start-tag
            <noscript>
  • Error Line 7, Column 85: required attribute "alt" not specified
    …      <img src="//cdn2.paytm.com/images/checkbox2.png" style="display: none" />

    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 9, Column 77: document type does not allow element "meta" here
            <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

    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 10, Column 23: document type does not allow element "title" here
                    <title>Online Recharge- Online Prepaid Mobile, DTH & DataCard R…

    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 10, Column 68: character "&" is the first character of a delimiter but occurred as data
    … Recharge- Online Prepaid Mobile, DTH & DataCard Recharge for Airtel,Vodafone,…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 12, Column 316: character "&" is the first character of a delimiter but occurred as data
    …odafone, Reliance, Idea, Tata Indicom & Docomo, Tata Sky, Dish TV, Tata Photon…

    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 12, Column 415: document type does not allow element "meta" here
    …ish TV, Tata Photon and all mobile, dth and datacard operator across India." />

    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 13, Column 102: document type does not allow element "meta" here
    …gle-site-verification" content="uy_KEeFtXW3kU4461yOZjwtS0lEtniVVE6V0Cw9mjL8" />

    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 15, Column 533: document type does not allow element "meta" here
    …echarge, loop mobile recharge, virgin mobile recharge, stel online recharge" />

    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 16, Column 63: document type does not allow element "meta" here
                    <meta name="Robots" content="index,  follow" />

    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 17, Column 49: document type does not allow element "meta" here
            <meta name="googlebot" content="noodp" />

    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 18, Column 54: document type does not allow element "meta" here
            <meta content="7 days" name="revisit-after" />

    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 19, Column 24: there is no attribute "property"
            <meta property="og:title" content="Paytm" />

    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 19, Column 52: document type does not allow element "meta" here
            <meta property="og:title" content="Paytm" />

    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 20, Column 69: document type does not allow element "meta" here
            <meta property="og:description" content="Awesome recharge" />

    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 21, Column 80: document type does not allow element "meta" here
            <meta property="og:image" content="//cdn2.paytm.com/images/Paytm.gif" />

    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 22, Column 97: document type does not allow element "link" here
    …"shortcut icon" href="//cdn2.paytm.com/images/paytm.ico" type="image/x-icon" />

    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 23, Column 76: document type does not allow element "link" here
            <link rel="publisher" href="https://plus.google.com/+paytm/posts" />

    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 24, Column 140: document type does not allow element "link" here
    …839ad922b7db4ee8a2227ed61797db/newmain.css" rel="stylesheet" type="text/css" />

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 27, Column 11: end tag for "object" omitted, but OMITTAG NO was specified
        </head>

    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 6, Column 9: start tag was here
            <noscript>
  • Error Line 27, Column 11: end tag for "head" which is not finished
        </head>

    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 37, Column 133: duplicate specification of attribute "id"
    …;padding: 10px; border-bottom: solid 1px #c3c3c3;display: none;" id="fblogin" >

    You have specified an attribute more than once. Example: Using the "height" attribute twice on the same "img" tag.

  • Error Line 43, Column 28: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    	<a href='/'><div id='logo'></div></a>

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

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

  • Warning Line 46, Column 86: cannot generate system identifier for general entity "key"
    …uest=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&ref…

    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 46, Column 86: general entity "key" not defined and no default entity
    …uest=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&ref…

    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 46, Column 89: reference not terminated by REFC delimiter
    …t=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referr…

    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 46, Column 89: reference to external entity in attribute value
    …t=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referr…

    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 46, Column 89: reference to entity "key" for which no system identifier could be generated
    …t=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referr…

    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 46, Column 85: entity was defined here
    …quest=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&re…
  • Warning Line 46, Column 123: cannot generate system identifier for general entity "referrer"
    …&key=f4a6a194427453cbdd15a02015d4b208&referrer=' class='mbg_def' id="opnsLogin…

    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 46, Column 123: general entity "referrer" not defined and no default entity
    …&key=f4a6a194427453cbdd15a02015d4b208&referrer=' class='mbg_def' id="opnsLogin…

    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 46, Column 131: reference not terminated by REFC delimiter
    …6a194427453cbdd15a02015d4b208&referrer=' class='mbg_def' id="opnsLogin"><span>…

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

  • Warning Line 46, Column 131: reference to external entity in attribute value
    …6a194427453cbdd15a02015d4b208&referrer=' class='mbg_def' id="opnsLogin"><span>…

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

  • Error Line 46, Column 131: reference to entity "referrer" for which no system identifier could be generated
    …6a194427453cbdd15a02015d4b208&referrer=' class='mbg_def' id="opnsLogin"><span>…

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

  • Info Line 46, Column 122: entity was defined here
    …l&key=f4a6a194427453cbdd15a02015d4b208&referrer=' class='mbg_def' id="opnsLogi…
  • Error Line 52, Column 8: required attribute "action" not specified
    		<form>

    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 54, Column 95: reference not terminated by REFC delimiter
    …t=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referr…

    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 54, Column 95: reference to external entity in attribute value
    …t=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referr…

    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 54, Column 95: reference to entity "key" for which no system identifier could be generated
    …t=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referr…

    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 46, Column 85: entity was defined here
    …quest=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&re…
  • Warning Line 54, Column 137: reference not terminated by REFC delimiter
    …6a194427453cbdd15a02015d4b208&referrer=" onclick="document.location.href='http…

    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 54, Column 137: reference to external entity in attribute value
    …6a194427453cbdd15a02015d4b208&referrer=" onclick="document.location.href='http…

    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 54, Column 137: reference to entity "referrer" for which no system identifier could be generated
    …6a194427453cbdd15a02015d4b208&referrer=" onclick="document.location.href='http…

    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 46, Column 122: entity was defined here
    …l&key=f4a6a194427453cbdd15a02015d4b208&referrer=' class='mbg_def' id="opnsLogi…
  • Warning Line 54, Column 250: reference not terminated by REFC delimiter
    …t=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referr…

    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 54, Column 250: reference to external entity in attribute value
    …t=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referr…

    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 54, Column 250: reference to entity "key" for which no system identifier could be generated
    …t=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referr…

    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 46, Column 85: entity was defined here
    …quest=https://www.paytm.com/index.html&key=f4a6a194427453cbdd15a02015d4b208&re…
  • Warning Line 54, Column 292: reference not terminated by REFC delimiter
    ….com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referrer='">Login</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 54, Column 292: reference to external entity in attribute value
    ….com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referrer='">Login</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 54, Column 292: reference to entity "referrer" for which no system identifier could be generated
    ….com/index.html&key=f4a6a194427453cbdd15a02015d4b208&referrer='">Login</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 46, Column 122: entity was defined here
    …l&key=f4a6a194427453cbdd15a02015d4b208&referrer=' class='mbg_def' id="opnsLogi…
  • Error Line 81, Column 26: syntax of attribute value does not conform to declared value
                    <div id="" style="">

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 102, Column 104: end tag for "input" omitted, but OMITTAG NO was specified
    …            <input type="hidden" id="validAmount"  name="validAmount" value="">

    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 102, Column 37: start tag was here
                                        <input type="hidden" id="validAmount"  name…
  • Error Line 109, Column 153: there is no attribute "autocomplete"
    …biNumber" maxlength="10" autocomplete='off' onkeypress="return isNumberKeyRCV(…

    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 149, Column 95: document type does not allow element "div" here; assuming missing "dd" start-tag
    …                            <div id='specialRechargeDiv' style='display: none'>
  • Error Line 165, Column 97: document type does not allow element "dd" here; assuming missing "dl" start-tag
    …                          <dd id="see_popular_recharge" style="display: none;">
  • Error Line 174, Column 107: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …d="amount" name="amount" autocomplete=OFF class="rch_amt" style="display: bloc…
  • Error Line 190, Column 129: end tag for "input" omitted, but OMITTAG NO was specified
    … recharge" id="idhere" name="Proceed"> <img src="//cdn2.paytm.com/images/ajax-…

    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 190, Column 41: start tag was here
    <input type="submit" class="btn" value="…
  • Error Line 190, Column 196: required attribute "alt" not specified
    …="Proceed"> <img src="//cdn2.paytm.com/images/ajax-loader-big.gif" id="loader">

    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 190, Column 197: end tag for "img" omitted, but OMITTAG NO was specified
    …="Proceed"> <img src="//cdn2.paytm.com/images/ajax-loader-big.gif" id="loader">

    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 190, Column 130: start tag was here
    …recharge" id="idhere" name="Proceed"> <img src="//cdn2.paytm.com/images/ajax-l…
  • Error Line 193, Column 55: end tag for "dd" omitted, but OMITTAG NO was specified
                                                    </form>

    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 149, Column 45: start tag was here
    <div id='specialRechargeDiv' style='disp…
  • Error Line 193, Column 55: end tag for "dl" omitted, but OMITTAG NO was specified
                                                    </form>

    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 130, Column 41: start tag was here
                                            <dl>
  • Error Line 275, Column 77: end tag for "select" which is not finished
                                                                        </select>

    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 279, Column 61: end tag for "dd" omitted, but OMITTAG NO was specified
                                                            </dl>

    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 272, Column 61: start tag was here
                                                                <dd>
  • Error Line 283, Column 61: end tag for element "dd" which is not open
                                                            </dd>

    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 304, Column 62: ID "biltype" already defined
                                                        <div id="biltype">

    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 86, Column 38: ID "biltype" first defined here
                                <div id="biltype">
  • Error Line 308, Column 180: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …lrchLandline" type="radio" name="radioUtility" class="styled"  checked=true /> 
  • Error Line 308, Column 180: value of attribute "checked" cannot be "true"; must be one of "checked"
    …lrchLandline" type="radio" name="radioUtility" class="styled"  checked=true /> 

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

  • Error Line 310, Column 80: ID "pre" already defined
    …                           <label id="pre" for="radioLandline">Landline</label…

    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 88, Column 169: ID "pre" first defined here
    …ame="radio" class="styled" checked="checked" /> <label id="pre">Prepaid</label>
  • Error Line 338, Column 99: ID "stype" already defined
    …                <input type="hidden" name="stype" id="stype" value="utility" />

    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 98, Column 75: ID "stype" first defined here
    …<input type="hidden" name="stype" id="stype" value="mobile" /> <input type="hi…
  • Error Line 347, Column 73: ID "mobile_opratorlst" already defined
    …                                                    <dd id="mobile_opratorlst">

    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 134, Column 53: ID "mobile_opratorlst" first defined here
                                                <dd id="mobile_opratorlst">
  • Error Line 351, Column 171: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …                    <option  selected value="Airtel Landline">Airtel Landline<…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 368, Column 136: end tag for "input" omitted, but OMITTAG NO was specified
    …                   value="Phone Number" style="margin-left: 5px;width: 224px;">

    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 366, Column 69: start tag was here
    <input id="phoneNumber" size="31" type="…
  • Error Line 411, Column 73: ID "amountid_dd" already defined
    …                                                          <dd id="amountid_dd">

    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 173, Column 53: ID "amountid_dd" first defined here
                                                <dd id="amountid_dd">
  • Error Line 412, Column 136: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …_landline" name="amount" autocomplete=OFF class="rch_amt" style="display: bloc…
  • Error Line 424, Column 105: ID "utilityType" already defined
    …nput type="hidden" name="utilityType" id="utilityType" value="BSES Rajdhani" />

    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 339, Column 105: ID "utilityType" first defined here
    …   <input type="hidden" name="utilityType" id="utilityType" value="landline" />
  • Error Line 425, Column 99: ID "stype" already defined
    …                <input type="hidden" name="stype" id="stype" value="utility" />

    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 98, Column 75: ID "stype" first defined here
    …<input type="hidden" name="stype" id="stype" value="mobile" /> <input type="hi…
  • Error Line 434, Column 94: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …                                <option selected value="Delhi" >Delhi</option> 

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 464, Column 169: syntax of attribute value does not conform to declared value
    …idth: 404px; padding-bottom: 5px" id="">Enter the exact bill amount payable .<…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 464, Column 170: document type does not allow element "span" here; missing one of "dt", "dd" start-tag
    …dth: 404px; padding-bottom: 5px" id="">Enter the exact bill amount payable .</…

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

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

  • Error Line 475, Column 99: ID "stype" already defined
    …            <input type="hidden" name="stype" id="stype" value="utility" />    

    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 98, Column 75: ID "stype" first defined here
    …<input type="hidden" name="stype" id="stype" value="mobile" /> <input type="hi…
  • Error Line 476, Column 105: ID "utilityType" already defined
    …  <input type="hidden" name="utilityType" id="utilityType" value="Toll Card" />

    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 339, Column 105: ID "utilityType" first defined here
    …   <input type="hidden" name="utilityType" id="utilityType" value="landline" />
  • Error Line 486, Column 94: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …                       <option selected value="DGTOLL" >Delhi-Gurgaon</option> 

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 494, Column 99: ID "subscribe_lbl" already defined
    …          <label for="SubscriberId" id="subscribe_lbl">Smart tag Number</label>

    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 214, Column 95: ID "subscribe_lbl" first defined here
    …             <label for="SubscriberId" id="subscribe_lbl">Subscriber ID</label>
  • Error Line 501, Column 120: ID "Subscriber_err_span" already defined
    …ry smtxt" style="display: block;" id="Subscriber_err_span">Enter your complete…

    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 220, Column 117: ID "Subscriber_err_span" first defined here
    …span class="gry smtxt" style="display: block;" id="Subscriber_err_span"></span>
  • Error Line 518, Column 87: ID "min_recharge_span" already defined
    …                    </span> <span id="min_recharge_span"></span> <span class="…

    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 234, Column 83: ID "min_recharge_span" first defined here
    …                    </span> <span id="min_recharge_span"></span> <span class="…
  • Error Line 520, Column 153: syntax of attribute value does not conform to declared value
    … text-align: left; width: 404px;" id="">Enter an amount specific to your Smart…

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 537, Column 105: required attribute "src" not specified
    …                                  <img id='imageID' border="0" usemap="#Map" />

    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 537, Column 105: required attribute "alt" not specified
    …                                  <img id='imageID' border="0" usemap="#Map" />

    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 539, Column 180: required attribute "alt" not specified
    …,267"  href="//www.paytm.com/blog/share-the-joy-of-travel/" target="_blank" /> 

    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 708, Column 79: document type does not allow element "script" here
                                                    <script type="text/javascript">

    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 257, Column 77: reference to non-existent ID "dc_operator"
    …                            <label for="dc_operator">Data Card Operator</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 270, Column 77: reference to non-existent ID "dc_operator"
    …                                        <label for="dc_operator">Circle</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 132, Column 61: reference to non-existent ID "opt"
    …                                       <label for="opt">Mobile Operator</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 345, Column 81: reference to non-existent ID "opt"
    …                                     <label for="opt">Landline Operator</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 106, Column 61: reference to non-existent ID "mobinumber"
    …                                  <label for="mobinumber">Mobile Number</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 358, Column 81: reference to non-existent ID "mobinumber"
    …                                <label for="mobinumber">Landline Number</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 480, Column 81: reference to non-existent ID "sel_opereator_route"
    …                                 <label for="sel_opereator_route">Route</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 119, Column 61: reference to non-existent ID "circle"
    …                                             <label for="circle">Circle</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 375, Column 81: reference to non-existent ID "circle"
    …                                             <label for="circle">Circle</label>

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 65.333 visits