Mailinator is a free, disposable email service for everyone who wants to protect their identity in blogs, forum and social media. ...

mailinator.com
  • Domain Name
    mailinator.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #16721
  • Page Size
    7.6 KB
  • Ip Address
    72.51.33.80
  • Heading
    H1: 1, H2: 1, H3: 3, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 2 PNG

Website Meta Analysis

  • Title
    Mailinator - Let Them Eat Spam!
  • Meta Keyword
    free, email, identity, identity theft, social media, security
  • Meta Description
    Mailinator is a free, disposable email service for everyone who wants to protect their identity in blogs, forum and social media.

Technical Analysis

  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    72.51.33.80
  • Domain Age
    9 Years, 6 Months, 14 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache-Coyote/1.1
  • content-type: text/html;charset=UTF-8
  • date: Thu, 24 Jan 2013 18:02:25 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Services Provided By:
Domain Bank, email
http://www.domainbank.com
Registrant:
Paul Tyma
1043 Noe Street
San Francisco, CA 94114
US
Registrar: DOMAINBANK
Domain Name: MAILINATOR.COM
Created: 02-JUL-03
Expires: 02-JUL-12
Updated: 15-JUN-11
Administrative, Technical Contact:
Tyma, Paul email
1043 Noe Street
San Francisco, CA 94114
US
4153774027

Name Servers:
NS1.PEER1.NET
NS2.PEER1.NET

DNS Analysis


DNS servers
ns1.peer1.net [69.90.13.5]
ns2.peer1.net [69.90.13.6]


DNS Records

Answer records
mailinator.com MX
preference: 10
exchange: mailinator.com
86400s
mailinator.com NS  ns1.peer1.net 259200s
mailinator.com NS  ns2.peer1.net 259200s
mailinator.com SOA
server: ns1.peer1.net
email: paul@manybrain.com
serial: 33
refresh: 25200
retry: 3600
expire: 172800
minimum ttl: 3600
3600s
mailinator.com TXT v=spf1 mx ptr -all 86400s
mailinator.com A 72.51.33.80 86400s

Authority records

Additional records
ns1.peer1.net A 69.90.13.5 21600s
ns2.peer1.net A 69.90.13.6 21600s

IP 72.51.33.80 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Los Angeles
  • Continent Code
    90017
  • Latitude
    213
  • Longitude
    803
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 72.51.33.80"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=72.51.33.80?showDetails=true&showARIN=false&ext=netref2
    #

    ServerBeach PEER1-SERVERBEACH-06A (NET-72-51-32-0-1) 72.51.32.0 - 72.51.47.255
    Peer 1 Network Inc. PEER1-BLK-08 (NET-72-51-0-0-1) 72.51.0.0 - 72.51.63.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 67 Errors
  • 20 Warnings
Ratio Text/Html
  • 0.6050710718401844
Message Error
  • Error Line 19, Column 66: end tag for "link" omitted, but OMITTAG NO was specified
        <link rel="stylesheet" type="text/css" href="css/global.css">

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

  • Info Line 19, Column 5: start tag was here
        <link rel="stylesheet" type="text/css" href="css/global.css">
  • Error Line 41, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 41, Column 1: start tag was here
    <br>
  • Error Line 46, Column 13: value of attribute "id" invalid: "4" cannot start a name
    <iframe id="4f974b14d4d2c" name="4f974b14d4d2c" src="http://us-ads.openx.net/w/…

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  • Warning Line 46, Column 100: cannot generate system identifier for general entity "cb"
    …s-ads.openx.net/w/1.0/afr?auid=191230&cb=INSERT_RANDOM_NUMBER_HERE" frameBorde…

    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 100: general entity "cb" not defined and no default entity
    …s-ads.openx.net/w/1.0/afr?auid=191230&cb=INSERT_RANDOM_NUMBER_HERE" frameBorde…

    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 102: reference not terminated by REFC delimiter
    …ads.openx.net/w/1.0/afr?auid=191230&cb=INSERT_RANDOM_NUMBER_HERE" frameBorder=…

    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 102: reference to external entity in attribute value
    …ads.openx.net/w/1.0/afr?auid=191230&cb=INSERT_RANDOM_NUMBER_HERE" frameBorder=…

    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 102: reference to entity "cb" for which no system identifier could be generated
    …ads.openx.net/w/1.0/afr?auid=191230&cb=INSERT_RANDOM_NUMBER_HERE" frameBorder=…

    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 99: entity was defined here
    …us-ads.openx.net/w/1.0/afr?auid=191230&cb=INSERT_RANDOM_NUMBER_HERE" frameBord…
  • Error Line 46, Column 142: there is no attribute "frameBorder"
    …NSERT_RANDOM_NUMBER_HERE" frameBorder="0" frameSpacing="0" scrolling="no" widt…

    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 46, Column 159: there is no attribute "frameSpacing"
    …ER_HERE" frameBorder="0" frameSpacing="0" scrolling="no" width="728" height="9…

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

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

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

  • Warning Line 46, Column 263: reference not terminated by REFC delimiter
    …openx.net/w/1.0/rc?cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 263: reference to external entity in attribute value
    …openx.net/w/1.0/rc?cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 263: reference to entity "cb" for which no system identifier could be generated
    …openx.net/w/1.0/rc?cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="h…

    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 99: entity was defined here
    …us-ads.openx.net/w/1.0/afr?auid=191230&cb=INSERT_RANDOM_NUMBER_HERE" frameBord…
  • Warning Line 46, Column 347: cannot generate system identifier for general entity "cs"
    …us-ads.openx.net/w/1.0/ai?auid=191230&cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER…

    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 347: general entity "cs" not defined and no default entity
    …us-ads.openx.net/w/1.0/ai?auid=191230&cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER…

    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 349: reference not terminated by REFC delimiter
    …-ads.openx.net/w/1.0/ai?auid=191230&cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER_H…

    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 349: reference to external entity in attribute value
    …-ads.openx.net/w/1.0/ai?auid=191230&cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER_H…

    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 349: reference to entity "cs" for which no system identifier could be generated
    …-ads.openx.net/w/1.0/ai?auid=191230&cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER_H…

    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 346: entity was defined here
    …/us-ads.openx.net/w/1.0/ai?auid=191230&cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBE…
  • Warning Line 46, Column 366: reference not terminated by REFC delimiter
    …1.0/ai?auid=191230&cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER_HERE" border="0" 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 46, Column 366: reference to external entity in attribute value
    …1.0/ai?auid=191230&cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER_HERE" border="0" 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 46, Column 366: reference to entity "cb" for which no system identifier could be generated
    …1.0/ai?auid=191230&cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER_HERE" border="0" 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 46, Column 99: entity was defined here
    …us-ads.openx.net/w/1.0/afr?auid=191230&cb=INSERT_RANDOM_NUMBER_HERE" frameBord…
  • Error Line 46, Column 415: end tag for "img" omitted, but OMITTAG NO was specified
    …&cs=4f974b14d4d2c&cb=INSERT_RANDOM_NUMBER_HERE" border="0" alt=""></a></iframe>

    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 46, Column 292: start tag was here
    …4d4d2c&cb=INSERT_RANDOM_NUMBER_HERE" ><img src="http://us-ads.openx.net/w/1.0/…
  • Error Line 82, Column 32: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
        <form name="search" method=get action="maildir.jsp">
  • Error Line 84, Column 72: value of attribute "align" cannot be "absmiddle"; must be one of "top", "middle", "bottom", "left", "right"
    …ut type="image" src="images/button_go.gif" align="absmiddle" class="buttonGo"/>

    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 97, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
                <br>

    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 97, Column 13: start tag was here
                <br>
  • Error Line 110, Column 69: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                <div style='text-align: center;width:90%;font-size:1em;'>

    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 111, Column 43: required attribute "alt" not specified
                    <img src='/get_alt_domain'>

    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 111, Column 44: end tag for "img" omitted, but OMITTAG NO was specified
                    <img src='/get_alt_domain'>

    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 111, Column 17: start tag was here
                    <img src='/get_alt_domain'>
  • Error Line 114, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
                <br>

    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 114, Column 13: start tag was here
                <br>
  • Error Line 116, Column 44: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
                <div style='text-align: center'>

    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 117, Column 56: end tag for "br" omitted, but OMITTAG NO was specified
                    still goes to Mailinator's inboxes!<br>

    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 117, Column 52: start tag was here
                    still goes to Mailinator's inboxes!<br>
  • Error Line 127, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
                <br>

    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 127, Column 13: start tag was here
                <br>
  • Error Line 129, Column 4: document type does not allow element "h3" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <h3><span>Get Your Mailinator Widget!</span></h3>

    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 131, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><a href=http://www.mailinator.com/widgetmaker.jsp>Customize</a> your OWN wid…

    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 131, Column 12: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <p><a href=http://www.mailinator.com/widgetmaker.jsp>Customize</a> your OWN wid…
  • Error Line 131, Column 18: NET-enabling start-tag not immediately followed by null end-tag
    <p><a href=http://www.mailinator.com/widgetmaker.jsp>Customize</a> your OWN wid…

    This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. The proper syntax is '... />' (note the position of the space).

  • Error Line 131, Column 66: end tag for element "a" which is not open
    …ef=http://www.mailinator.com/widgetmaker.jsp>Customize</a> your OWN widget!</p>

    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 134, Column 15: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe width=267 height=250 marginwidth=0 marginheight=0 scrolling=no framebor…
  • Error Line 134, Column 26: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    <iframe width=267 height=250 marginwidth=0 marginheight=0 scrolling=no framebor…
  • Error Line 134, Column 42: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …rame width=267 height=250 marginwidth=0 marginheight=0 scrolling=no frameborde…
  • Error Line 134, Column 57: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …me width=267 height=250 marginwidth=0 marginheight=0 scrolling=no frameborder=0
  • Error Line 134, Column 69: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …me width=267 height=250 marginwidth=0 marginheight=0 scrolling=no frameborder=0
  • Error Line 134, Column 84: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified
    …me width=267 height=250 marginwidth=0 marginheight=0 scrolling=no frameborder=0
  • Warning Line 135, Column 66: cannot generate system identifier for general entity "h"
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

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

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

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

  • Error Line 135, Column 66: general entity "h" not defined and no default entity
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Warning Line 135, Column 67: reference not terminated by REFC delimiter
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Warning Line 135, Column 67: reference to external entity in attribute value
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Error Line 135, Column 67: reference to entity "h" for which no system identifier could be generated
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Info Line 135, Column 65: entity was defined here
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>
  • Warning Line 135, Column 72: cannot generate system identifier for general entity "b"
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

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

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

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

  • Error Line 135, Column 72: general entity "b" not defined and no default entity
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Warning Line 135, Column 73: reference not terminated by REFC delimiter
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Warning Line 135, Column 73: reference to external entity in attribute value
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Error Line 135, Column 73: reference to entity "b" for which no system identifier could be generated
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Info Line 135, Column 71: entity was defined here
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>
  • Warning Line 135, Column 81: cannot generate system identifier for general entity "f"
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

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

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

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

  • Error Line 135, Column 81: general entity "f" not defined and no default entity
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Warning Line 135, Column 82: reference not terminated by REFC delimiter
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Warning Line 135, Column 82: reference to external entity in attribute value
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Error Line 135, Column 82: reference to entity "f" for which no system identifier could be generated
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>

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

  • Info Line 135, Column 80: entity was defined here
    …//www.mailinator.com/widget/mailin8r.jsp?w=267&h=250&b=foobat&f=true'></iframe>
  • Error Line 139, Column 14: end tag for "p" omitted, but OMITTAG NO was specified
            </div>

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

  • Info Line 107, Column 13: start tag was here
                <p>
  • Error Line 154, Column 91: end tag for "br" omitted, but OMITTAG NO was specified
    …         Use <strong>any</strong> inbox that <strong>YOU</strong> think up!<br>

    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 154, Column 87: start tag was here
    …         Use <strong>any</strong> inbox that <strong>YOU</strong> think up!<br>
  • Error Line 155, Column 46: end tag for "br" omitted, but OMITTAG NO was specified
                        Here's a suggestion: <br> <br>

    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 155, Column 42: start tag was here
                        Here's a suggestion: <br> <br>
  • Error Line 155, Column 51: end tag for "br" omitted, but OMITTAG NO was specified
                        Here's a suggestion: <br> <br>

    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 155, Column 47: start tag was here
                        Here's a suggestion: <br> <br>
  • Error Line 167, Column 24: document type does not allow element "br" here; assuming missing "li" start-tag
                        <br>
  • Error Line 167, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
                        <br>

    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 167, Column 21: start tag was here
                        <br>
  • Error Line 168, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li>No Sign-up</li>

    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 169, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
                        <br>

    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 169, Column 21: start tag was here
                        <br>
  • Error Line 170, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li>Inboxes are created when email arrives for them</li>

    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 171, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
                        <br>

    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 171, Column 21: start tag was here
                        <br>
  • Error Line 172, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li>Make up email addresses on the fly</li>

    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 173, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
                        <br>

    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 173, Column 21: start tag was here
                        <br>
  • Error Line 174, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li>Make-up address, give it to others, come here and check…

    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 175, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
                        <br>

    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 175, Column 21: start tag was here
                        <br>
  • Error Line 176, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li>RSS/Atom feeds for every Inbox</li>

    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 177, Column 25: end tag for "br" omitted, but OMITTAG NO was specified
                        <br>

    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 177, Column 21: start tag was here
                        <br>
  • Error Line 178, Column 24: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                        <li>Give out a Mailinator address any time you need an emai…

    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 180, Column 21: end tag for "li" omitted, but OMITTAG NO was specified
                    </ul>

    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 167, Column 21: start tag was here
                        <br>
  • Error Line 207, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 207, Column 1: start tag was here
    <br>
  • Error Line 215, Column 63: required attribute "type" not specified
    …ect.facebook.net/en_US/all.js#xfbml=1"></script><fb:like-box href="http://www.…

    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 215, Column 91: there is no attribute "href"
    …s#xfbml=1"></script><fb:like-box href="http://www.facebook.com/pages/Mailinato…

    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 215, Column 152: there is no attribute "width"
    …m/pages/Mailinator/90939329099" width="250" show_faces="true" border_color="" …

    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 215, Column 169: there is no attribute "show_faces"
    …r/90939329099" width="250" show_faces="true" border_color="" stream="false" he…

    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 215, Column 189: there is no attribute "border_color"
    …="250" show_faces="true" border_color="" stream="false" header="true"></fb:lik…

    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 215, Column 199: there is no attribute "stream"
    …" show_faces="true" border_color="" stream="false" header="true"></fb:like-box>

    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 215, Column 214: there is no attribute "header"
    …" show_faces="true" border_color="" stream="false" header="true"></fb:like-box>

    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 215, Column 220: element "fb:like-box" undefined
    …" show_faces="true" border_color="" stream="false" header="true"></fb:like-box>

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

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 218, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 218, Column 1: start tag was here
    <br>

Visitor Analysis

Daily Visitor
  • 9.917 visits
Daily Visitor