From its beginnings a half-century ago, Stony Brook University has been characterized by innovation, energy, and progress, transforming the lives of people who earn degrees, work, and make groundbreaking discoveries here. A dramatic ...

stonybrook.edu
  • Domain Name
    stonybrook.edu
  • Favicon
  • Google Page Rank
    7
  • Alexa Rank
    #22924
  • Page Size
    33.9 KB
  • Ip Address
    129.49.2.176
  • Heading
    H1: 1, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    19 GIF, 18 JPG, 0 PNG

Website Meta Analysis

  • Title
    Stony Brook University, Stony Brook, New York
  • Meta Keyword
    Stony Brook University, SUNY Stony Brook, SUNY-SB, SUNYSB, U of Stony Brook, research university, summer session, University of Stony Brook, University at Stony Brook, Stonybrook, Admissions, College, Undergraduate, Sciences, Liberal Arts, New York, Long Island
  • Meta Description
    From its beginnings a half-century ago, Stony Brook University has been characterized by innovation, energy, and progress, transforming the lives of people who earn degrees, work, and make groundbreaking discoveries here. A dramatic trajectory of growth has turned what was once a small teacher preparation college into an internationally recognized research institution that is changing the world.

Technical Analysis

  • Webserver
    Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/0.9.8m
  • Ip Address
    129.49.2.176
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from stonybrook.edu.

HTML Analysis

  • date: Thu, 31 Jan 2013 12:31:02 GMT
  • server: Apache/2.2.15 (Unix) mod_ssl/2.2.15 OpenSSL/0.9.8m
  • accept-ranges: bytes
  • content-type: text/html
  • content-length: 35107
  • age: 19
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)

This Registry database contains ONLY .EDU domains.
The data in the EDUCAUSE Whois database is provided
by EDUCAUSE for information purposes in order to
assist in the process of obtaining information about
or related to .edu domain registration records.

The EDUCAUSE Whois database is authoritative for the
.EDU domain.

A Web interface for the .EDU EDUCAUSE Whois Server is
available at: http://whois.educause.net

By submitting a Whois query, you agree that this information
will not be used to allow, enable, or otherwise support
the transmission of unsolicited commercial advertising or
solicitations via e-mail. The use of electronic processes to
harvest information from this server is generally prohibited
except as reasonably necessary to register or modify .edu
domain names.

You may use "%" as a wildcard in your search. For further
information regarding the use of this WHOIS server, please
type: help

--------------------------

Domain Name: STONYBROOK.EDU

Registrant:
State University of New York/Stony Brook
Stony Brook University
Stony Brook, NY 11794-2630
UNITED STATES

Administrative Contact:
Behzad Barzideh
TeLNeT
241 ECC Building
Stony Brook, NY 11794-2630
UNITED STATES
(631) 632-8031
email

Technical Contact:
TeLNeT
Service Desk
Stony Brook University
ECC Build. Room 247
Stony Brook, NY 11794-2630
UNITED STATES
(631) 772-9231
email

Name Servers:
NOCNOC.STONYBROOK.EDU 129.49.7.3
WHOISTHERE.STONYBROOK.EDU 129.49.7.250
MEWHO.STONYBROOK.EDU 199.110.254.244

Domain record activated: 29-Apr-1996
Domain record last updated: 25-Aug-2011
Domain expires: 31-Jul-2012


DNS Analysis


DNS servers
nocnoc.stonybrook.edu [129.49.7.3]
whoisthere.stonybrook.edu [129.49.7.250]
mewho.stonybrook.edu [199.110.254.244]


DNS Records

Answer records
stonybrook.edu SOA
server: itisme-a.stonybrook.edu
email: dns@noc.stonybrook.edu
serial: 2012070364
refresh: 3600
retry: 3600
expire: 2419200
minimum ttl: 300
300s
stonybrook.edu NS  mewho.stonybrook.edu 300s
stonybrook.edu NS  whoisthere.stonybrook.edu 300s
stonybrook.edu NS  nocnoc.stonybrook.edu 300s
stonybrook.edu A 129.49.2.176 300s
stonybrook.edu MX
preference: 1
exchange: sbmta1.cc.stonybrook.edu
300s
stonybrook.edu MX
preference: 1
exchange: sbmta2.cc.stonybrook.edu
300s
stonybrook.edu TXT google-site-verification=7D4xsTI9K41YwGJ7xvEmaENCliprxvh3atJpuUqdDb0 300s

Authority records

Additional records
mewho.stonybrook.edu A 199.110.254.244 300s
nocnoc.stonybrook.edu A 129.49.7.3 300s
whoisthere.stonybrook.edu A 129.49.7.250 300s
sbmta1.cc.stonybrook.edu A 129.49.2.21 3600s
sbmta2.cc.stonybrook.edu A 129.49.2.199 3600s

IP 129.49.2.176 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Stony Brook
  • Continent Code
    11794
  • Latitude
    631
  • Longitude
    501
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 129.49.2.176"
    #
    # Use "?" to get help.
    #

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

    NetRange: 129.49.0.0 - 129.49.255.255
    CIDR: 129.49.0.0/16
    OriginAS:
    NetName: SUNY-SB
    NetHandle: NET-129-49-0-0-1
    Parent: NET-129-0-0-0-0
    NetType: Direct Assignment
    RegDate: 1987-08-03
    Updated: 1999-06-23
    Ref: http://whois.arin.net/rest/net/NET-129-49-0-0-1

    OrgName: State University of New York at Stony Brook
    OrgId: SUNYASB
    Address: 247 ECC Building
    City: Stony Brook
    StateProv: NY
    PostalCode: 11794-2620
    Country: US
    RegDate: 1985-08-07
    Updated: 2011-12-22
    Comment: Contact abuse@stonybrook.edu
    Ref: http://whois.arin.net/rest/org/SUNYASB

    OrgAbuseHandle: BB3872-ARIN
    OrgAbuseName: Barzideh, Behzad
    OrgAbusePhone: +1-631-632-2899
    OrgAbuseEmail: behzad.barzideh@stonybrook.edu
    OrgAbuseRef: http://whois.arin.net/rest/poc/BB3872-ARIN

    OrgTechHandle: BB3872-ARIN
    OrgTechName: Barzideh, Behzad
    OrgTechPhone: +1-631-632-2899
    OrgTechEmail: behzad.barzideh@stonybrook.edu
    OrgTechRef: http://whois.arin.net/rest/poc/BB3872-ARIN

    RTechHandle: JS585-ARIN
    RTechName: Stier, John
    RTechPhone: +1-516-632-8017
    RTechEmail: John.Stier@sunysb.edu
    RTechRef: http://whois.arin.net/rest/poc/JS585-ARIN

    #
    # 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
  • 78 Errors
  • 74 Warnings
Ratio Text/Html
  • 0.6272324000460883
Message Error
  • Error Line 45, Column 18: there is no attribute "HTTP-EQUIV"
    <META HTTP-EQUIV="Pragma" CONTENT="no-cache">

    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 45, Column 35: there is no attribute "CONTENT"
    <META HTTP-EQUIV="Pragma" CONTENT="no-cache">

    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 45, Column 45: element "META" undefined
    <META HTTP-EQUIV="Pragma" CONTENT="no-cache">

    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 49, Column 52: element "META" undefined
    <META HTTP-EQUIV="Cache-Control" CONTENT="no-cache">

    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 53, Column 55: element "META" undefined
    <META HTTP-EQUIV="Pragma-directive" CONTENT="no-cache">

    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 57, Column 54: element "META" undefined
    <META HTTP-EQUIV="Cache-Directive" CONTENT="no-cache">

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

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

    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 73, Column 16: there is no attribute "NAME"
        <META NAME="Keywords" CONTENT="Stony  Brook University, SUNY Stony Brook,

    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 85, Column 221: element "META" undefined
    …ssions, College, Undergraduate, Sciences, Liberal Arts, New York, Long Island">

    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 97, Column 435: element "META" undefined
    … internationally recognized research institution that is changing the world. ">

    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).
  • Warning Line 141, Column 52: character "&" is the first character of a delimiter but occurred as data
    	if (typeof navigator.cookieEnabled == "undefined" && !cookieEnabled){ 

    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 141, Column 53: character "&" is the first character of a delimiter but occurred as data
    	if (typeof navigator.cookieEnabled == "undefined" && !cookieEnabled){ 

    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 159, Column 23: character "&" is the first character of a delimiter but occurred as data
    	var re = new RegExp('&'+q+'(?:=([^&]*))?(?=&|$)','i'); 

    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 159, Column 36: character "&" is the first character of a delimiter but occurred as data
    	var re = new RegExp('&'+q+'(?:=([^&]*))?(?=&|$)','i'); 

    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 159, Column 45: character "&" is the first character of a delimiter but occurred as data
    	var re = new RegExp('&'+q+'(?:=([^&]*))?(?=&|$)','i'); 

    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 161, Column 29: character "&" is the first character of a delimiter but occurred as data
    	return (s=s.replace(/^\?/,'&').match(re)) ? (typeof s[1] == 'undefined' ? '' :…

    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 185, Column 8: required attribute "type" not specified
    <script>

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

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

  • Error Line 212, Column 7: end tag for "META" 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 97, Column 1: start tag was here
    <META NAME="Description" CONTENT="From its beginnings a half-century ago, Stony…
  • Error Line 212, Column 7: end tag for "META" 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 73, Column 5: start tag was here
        <META NAME="Keywords" CONTENT="Stony  Brook University, SUNY Stony Brook,
  • Error Line 212, Column 7: end tag for "META" 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 61, Column 1: start tag was here
    <META HTTP-EQUIV="Expires" CONTENT="0">
  • Error Line 212, Column 7: end tag for "META" 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 57, Column 1: start tag was here
    <META HTTP-EQUIV="Cache-Directive" CONTENT="no-cache">
  • Error Line 212, Column 7: end tag for "META" 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 53, Column 1: start tag was here
    <META HTTP-EQUIV="Pragma-directive" CONTENT="no-cache">
  • Error Line 212, Column 7: end tag for "META" 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 49, Column 1: start tag was here
    <META HTTP-EQUIV="Cache-Control" CONTENT="no-cache">
  • Error Line 212, Column 7: end tag for "META" 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 45, Column 1: start tag was here
    <META HTTP-EQUIV="Pragma" CONTENT="no-cache">
  • Error Line 212, Column 7: 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 398, Column 24: document type does not allow element "style" here
     <style type="text/css">

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

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

  • Error Line 487, Column 66: end tag for "input" omitted, but OMITTAG NO was specified
         <input type="hidden" name="client" value="default_frontend">

    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 487, Column 6: start tag was here
         <input type="hidden" name="client" value="default_frontend">
  • Error Line 488, Column 70: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="proxystylesheet" value="default_frontend">

    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 488, Column 1: start tag was here
    <input type="hidden" name="proxystylesheet" value="default_frontend">
  • Error Line 489, Column 61: end tag for "input" omitted, but OMITTAG NO was specified
    <input type="hidden" name="site" value="default_collection">

    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 489, Column 1: start tag was here
    <input type="hidden" name="site" value="default_collection">
  • Error Line 495, Column 17: end tag for "br" omitted, but OMITTAG NO was specified
                <br>             <input name="searchType" type="radio" value="0" id…

    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 495, Column 13: start tag was here
                <br>             <input name="searchType" type="radio" value="0" id…
  • Error Line 561, Column 7: end tag for element "form" which is not open
    </form>

    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.

  • Warning Line 599, Column 46: character "&" is the first character of a delimiter but occurred as data
    <li id="calendars"><a href="arts.shtml">Arts & Culture</a></li>

    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 611, Column 8: end tag for element "div" which is not open
      </div>

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

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

  • Warning Line 640, Column 90: cannot generate system identifier for general entity "todate"
    …rook/EventList.aspx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=publ…

    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 640, Column 90: general entity "todate" not defined and no default entity
    …rook/EventList.aspx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=publ…

    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 640, Column 96: reference not terminated by REFC delimiter
    …ventList.aspx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=public&eve…

    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 640, Column 96: reference to external entity in attribute value
    …ventList.aspx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=public&eve…

    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 640, Column 96: reference to entity "todate" for which no system identifier could be generated
    …ventList.aspx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=public&eve…

    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 640, Column 89: entity was defined here
    …brook/EventList.aspx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=pub…
  • Warning Line 640, Column 107: cannot generate system identifier for general entity "display"
    …px?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398…

    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 640, Column 107: general entity "display" not defined and no default entity
    …px?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398…

    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 640, Column 114: reference not terminated by REFC delimiter
    …date=2/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=E…

    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 640, Column 114: reference to external entity in attribute value
    …date=2/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=E…

    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 640, Column 114: reference to entity "display" for which no system identifier could be generated
    …date=2/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=E…

    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 640, Column 106: entity was defined here
    …spx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=1239…
  • Warning Line 640, Column 121: cannot generate system identifier for general entity "type"
    …1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDet…

    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 640, Column 121: general entity "type" not defined and no default entity
    …1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDet…

    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 640, Column 125: reference not terminated by REFC delimiter
    …13&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDetails…

    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 640, Column 125: reference to external entity in attribute value
    …13&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDetails…

    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 640, Column 125: reference to entity "type" for which no system identifier could be generated
    …13&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDetails…

    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 640, Column 120: entity was defined here
    …/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDe…
  • Warning Line 640, Column 133: cannot generate system identifier for general entity "eventidn"
    …e=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDetails&informa…

    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 640, Column 133: general entity "eventidn" not defined and no default entity
    …e=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDetails&informa…

    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 640, Column 141: reference not terminated by REFC delimiter
    …013&display=Month&type=public&eventidn=12398&view=EventDetails&information_id=…

    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 640, Column 141: reference to external entity in attribute value
    …013&display=Month&type=public&eventidn=12398&view=EventDetails&information_id=…

    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 640, Column 141: reference to entity "eventidn" for which no system identifier could be generated
    …013&display=Month&type=public&eventidn=12398&view=EventDetails&information_id=…

    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 640, Column 132: entity was defined here
    …te=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDetails&inform…
  • Warning Line 640, Column 148: cannot generate system identifier for general entity "view"
    …play=Month&type=public&eventidn=12398&view=EventDetails&information_id=38088">…

    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 640, Column 148: general entity "view" not defined and no default entity
    …play=Month&type=public&eventidn=12398&view=EventDetails&information_id=38088">…

    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 640, Column 152: reference not terminated by REFC delimiter
    …=Month&type=public&eventidn=12398&view=EventDetails&information_id=38088"><img…

    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 640, Column 152: reference to external entity in attribute value
    …=Month&type=public&eventidn=12398&view=EventDetails&information_id=38088"><img…

    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 640, Column 152: reference to entity "view" for which no system identifier could be generated
    …=Month&type=public&eventidn=12398&view=EventDetails&information_id=38088"><img…

    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 640, Column 147: entity was defined here
    …splay=Month&type=public&eventidn=12398&view=EventDetails&information_id=38088"…
  • Warning Line 640, Column 166: cannot generate system identifier for general entity "information_id"
    …blic&eventidn=12398&view=EventDetails&information_id=38088"><img src="data1/im…

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

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

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

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

  • Error Line 640, Column 166: general entity "information_id" not defined and no default entity
    …blic&eventidn=12398&view=EventDetails&information_id=38088"><img src="data1/im…

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

  • Warning Line 640, Column 180: reference not terminated by REFC delimiter
    …12398&view=EventDetails&information_id=38088"><img src="data1/images/amanpour.…

    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 640, Column 180: reference to external entity in attribute value
    …12398&view=EventDetails&information_id=38088"><img src="data1/images/amanpour.…

    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 640, Column 180: reference to entity "information_id" for which no system identifier could be generated
    …12398&view=EventDetails&information_id=38088"><img src="data1/images/amanpour.…

    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 640, Column 165: entity was defined here
    …ublic&eventidn=12398&view=EventDetails&information_id=38088"><img src="data1/i…
  • Error Line 921, Column 145: "border:0" is not a member of a group specified for any attribute
    …hred_the_Competiton_in.shtml" border:0;"><img src="images/morelighter.gif" alt…
  • Error Line 921, Column 237: end tag for "br" omitted, but OMITTAG NO was specified
    …images/morelighter.gif" alt="more" width="49" height="15" border="0" /></a><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 921, Column 233: start tag was here
    …images/morelighter.gif" alt="more" width="49" height="15" border="0" /></a><br>
  • Error Line 934, Column 287: end tag for "img" omitted, but OMITTAG NO was specified
    …src="images/morelighter.gif" alt="more" width="49" height="15" border="0" ></a>

    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 934, Column 204: start tag was here
    …_University.shtml"  style="border:0;"><img src="images/morelighter.gif" alt="m…
  • Error Line 939, 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://sb.cc.stonybrook.edu/happenings/oncampus/stony-brooks-ng…

    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 946, Column 127: "border:0" is not a member of a group specified for any attribute
    …linic-to-be-held-february-9/" border:0;"><img src="images/morelighter.gif" alt…
  • Error Line 946, Column 219: end tag for "br" omitted, but OMITTAG NO was specified
    …images/morelighter.gif" alt="more" width="49" height="15" border="0" /></a><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 946, Column 215: start tag was here
    …images/morelighter.gif" alt="more" width="49" height="15" border="0" /></a><br>
  • Error Line 951, 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 951, Column 1: start tag was here
    <br>
  • Error Line 964, 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 964, Column 1: start tag was here
    <br>
  • Error Line 965, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p><br />

    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 981, Column 8: 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 939, Column 1: start tag was here
    <p>    <a href="http://sb.cc.stonybrook.edu/happenings/oncampus/stony-brooks-ng…
  • Error Line 981, Column 8: 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 929, Column 1: start tag was here
    <p><a href="http://commcgi.cc.stonybrook.edu/am2/publish/General_University_New…
  • Error Line 1015, Column 52: document type does not allow element "td" here; assuming missing "tr" start-tag
    …           <td width="47" valign="top"><div align="right" class="bluetext"><st…
  • Warning Line 1017, Column 94: reference not terminated by REFC delimiter
    …ventList.aspx?fromdate=1/1/2013&todate=1/31/2013&display=Month&type=public&eve…

    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 1017, Column 94: reference to external entity in attribute value
    …ventList.aspx?fromdate=1/1/2013&todate=1/31/2013&display=Month&type=public&eve…

    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 1017, Column 94: reference to entity "todate" for which no system identifier could be generated
    …ventList.aspx?fromdate=1/1/2013&todate=1/31/2013&display=Month&type=public&eve…

    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 640, Column 89: entity was defined here
    …brook/EventList.aspx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=pub…
  • Warning Line 1017, Column 112: reference not terminated by REFC delimiter
    …date=1/1/2013&todate=1/31/2013&display=Month&type=public&eventidn=12378&view=E…

    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 1017, Column 112: reference to external entity in attribute value
    …date=1/1/2013&todate=1/31/2013&display=Month&type=public&eventidn=12378&view=E…

    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 1017, Column 112: reference to entity "display" for which no system identifier could be generated
    …date=1/1/2013&todate=1/31/2013&display=Month&type=public&eventidn=12378&view=E…

    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 640, Column 106: entity was defined here
    …spx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=1239…
  • Warning Line 1017, Column 123: reference not terminated by REFC delimiter
    …13&todate=1/31/2013&display=Month&type=public&eventidn=12378&view=EventDetails…

    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 1017, Column 123: reference to external entity in attribute value
    …13&todate=1/31/2013&display=Month&type=public&eventidn=12378&view=EventDetails…

    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 1017, Column 123: reference to entity "type" for which no system identifier could be generated
    …13&todate=1/31/2013&display=Month&type=public&eventidn=12378&view=EventDetails…

    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 640, Column 120: entity was defined here
    …/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDe…
  • Warning Line 1017, Column 139: reference not terminated by REFC delimiter
    …013&display=Month&type=public&eventidn=12378&view=EventDetails&information_id=…

    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 1017, Column 139: reference to external entity in attribute value
    …013&display=Month&type=public&eventidn=12378&view=EventDetails&information_id=…

    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 1017, Column 139: reference to entity "eventidn" for which no system identifier could be generated
    …013&display=Month&type=public&eventidn=12378&view=EventDetails&information_id=…

    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 640, Column 132: entity was defined here
    …te=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDetails&inform…
  • Warning Line 1017, Column 150: reference not terminated by REFC delimiter
    …=Month&type=public&eventidn=12378&view=EventDetails&information_id=38048" styl…

    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 1017, Column 150: reference to external entity in attribute value
    …=Month&type=public&eventidn=12378&view=EventDetails&information_id=38048" styl…

    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 1017, Column 150: reference to entity "view" for which no system identifier could be generated
    …=Month&type=public&eventidn=12378&view=EventDetails&information_id=38048" styl…

    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 640, Column 147: entity was defined here
    …splay=Month&type=public&eventidn=12398&view=EventDetails&information_id=38088"…
  • Warning Line 1017, Column 178: reference not terminated by REFC delimiter
    …12378&view=EventDetails&information_id=38048" style="border:0;">Black History …

    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 1017, Column 178: reference to external entity in attribute value
    …12378&view=EventDetails&information_id=38048" style="border:0;">Black History …

    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 1017, Column 178: reference to entity "information_id" for which no system identifier could be generated
    …12378&view=EventDetails&information_id=38048" style="border:0;">Black History …

    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 640, Column 165: entity was defined here
    …ublic&eventidn=12398&view=EventDetails&information_id=38088"><img src="data1/i…
  • Error Line 1023, Column 49: document type does not allow element "td" here; assuming missing "tr" start-tag
    …                      <td valign="top"><div align="right" class="bluetext"><st…
  • Warning Line 1025, Column 94: reference not terminated by REFC delimiter
    …ventList.aspx?fromdate=1/1/2013&todate=1/31/2013&display=Month&type=public&eve…

    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 1025, Column 94: reference to external entity in attribute value
    …ventList.aspx?fromdate=1/1/2013&todate=1/31/2013&display=Month&type=public&eve…

    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 1025, Column 94: reference to entity "todate" for which no system identifier could be generated
    …ventList.aspx?fromdate=1/1/2013&todate=1/31/2013&display=Month&type=public&eve…

    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 640, Column 89: entity was defined here
    …brook/EventList.aspx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=pub…
  • Warning Line 1025, Column 112: reference not terminated by REFC delimiter
    …date=1/1/2013&todate=1/31/2013&display=Month&type=public&eventidn=12187&view=E…

    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 1025, Column 112: reference to external entity in attribute value
    …date=1/1/2013&todate=1/31/2013&display=Month&type=public&eventidn=12187&view=E…

    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 1025, Column 112: reference to entity "display" for which no system identifier could be generated
    …date=1/1/2013&todate=1/31/2013&display=Month&type=public&eventidn=12187&view=E…

    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 640, Column 106: entity was defined here
    …spx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=1239…
  • Warning Line 1025, Column 123: reference not terminated by REFC delimiter
    …13&todate=1/31/2013&display=Month&type=public&eventidn=12187&view=EventDetails…

    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 1025, Column 123: reference to external entity in attribute value
    …13&todate=1/31/2013&display=Month&type=public&eventidn=12187&view=EventDetails…

    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 1025, Column 123: reference to entity "type" for which no system identifier could be generated
    …13&todate=1/31/2013&display=Month&type=public&eventidn=12187&view=EventDetails…

    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 640, Column 120: entity was defined here
    …/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDe…
  • Warning Line 1025, Column 139: reference not terminated by REFC delimiter
    …013&display=Month&type=public&eventidn=12187&view=EventDetails&information_id=…

    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 1025, Column 139: reference to external entity in attribute value
    …013&display=Month&type=public&eventidn=12187&view=EventDetails&information_id=…

    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 1025, Column 139: reference to entity "eventidn" for which no system identifier could be generated
    …013&display=Month&type=public&eventidn=12187&view=EventDetails&information_id=…

    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 640, Column 132: entity was defined here
    …te=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDetails&inform…
  • Warning Line 1025, Column 150: reference not terminated by REFC delimiter
    …=Month&type=public&eventidn=12187&view=EventDetails&information_id=37617" styl…

    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 1025, Column 150: reference to external entity in attribute value
    …=Month&type=public&eventidn=12187&view=EventDetails&information_id=37617" styl…

    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 1025, Column 150: reference to entity "view" for which no system identifier could be generated
    …=Month&type=public&eventidn=12187&view=EventDetails&information_id=37617" styl…

    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 640, Column 147: entity was defined here
    …splay=Month&type=public&eventidn=12398&view=EventDetails&information_id=38088"…
  • Warning Line 1025, Column 178: reference not terminated by REFC delimiter
    …12187&view=EventDetails&information_id=37617" style="border:0;">Women's Basket…

    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 1025, Column 178: reference to external entity in attribute value
    …12187&view=EventDetails&information_id=37617" style="border:0;">Women's Basket…

    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 1025, Column 178: reference to entity "information_id" for which no system identifier could be generated
    …12187&view=EventDetails&information_id=37617" style="border:0;">Women's Basket…

    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 640, Column 165: entity was defined here
    …ublic&eventidn=12398&view=EventDetails&information_id=38088"><img src="data1/i…
  • Error Line 1030, Column 49: document type does not allow element "td" here; assuming missing "tr" start-tag
    …                      <td valign="top"><div align="right" class="bluetext"><st…
  • Warning Line 1032, Column 94: reference not terminated by REFC delimiter
    …ventList.aspx?fromdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventi…

    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 1032, Column 94: reference to external entity in attribute value
    …ventList.aspx?fromdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventi…

    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 1032, Column 94: reference to entity "todate" for which no system identifier could be generated
    …ventList.aspx?fromdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventi…

    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 640, Column 89: entity was defined here
    …brook/EventList.aspx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=pub…
  • Warning Line 1032, Column 111: reference not terminated by REFC delimiter
    …mdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventidn=12395&view=Eve…

    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 1032, Column 111: reference to external entity in attribute value
    …mdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventidn=12395&view=Eve…

    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 1032, Column 111: reference to entity "display" for which no system identifier could be generated
    …mdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventidn=12395&view=Eve…

    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 640, Column 106: entity was defined here
    …spx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=1239…
  • Warning Line 1032, Column 120: reference not terminated by REFC delimiter
    …/2013&todate=2/1/2013&display=Day&type=public&eventidn=12395&view=EventDetails…

    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 1032, Column 120: reference to external entity in attribute value
    …/2013&todate=2/1/2013&display=Day&type=public&eventidn=12395&view=EventDetails…

    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 1032, Column 120: reference to entity "type" for which no system identifier could be generated
    …/2013&todate=2/1/2013&display=Day&type=public&eventidn=12395&view=EventDetails…

    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 640, Column 120: entity was defined here
    …/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDe…
  • Warning Line 1032, Column 136: reference not terminated by REFC delimiter
    …/2013&display=Day&type=public&eventidn=12395&view=EventDetails&information_id=…

    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 1032, Column 136: reference to external entity in attribute value
    …/2013&display=Day&type=public&eventidn=12395&view=EventDetails&information_id=…

    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 1032, Column 136: reference to entity "eventidn" for which no system identifier could be generated
    …/2013&display=Day&type=public&eventidn=12395&view=EventDetails&information_id=…

    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 640, Column 132: entity was defined here
    …te=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDetails&inform…
  • Warning Line 1032, Column 147: reference not terminated by REFC delimiter
    …ay=Day&type=public&eventidn=12395&view=EventDetails&information_id=38082" styl…

    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 1032, Column 147: reference to external entity in attribute value
    …ay=Day&type=public&eventidn=12395&view=EventDetails&information_id=38082" styl…

    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 1032, Column 147: reference to entity "view" for which no system identifier could be generated
    …ay=Day&type=public&eventidn=12395&view=EventDetails&information_id=38082" styl…

    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 640, Column 147: entity was defined here
    …splay=Month&type=public&eventidn=12398&view=EventDetails&information_id=38088"…
  • Warning Line 1032, Column 175: reference not terminated by REFC delimiter
    …12395&view=EventDetails&information_id=38082" style="border:0;">Distinguished …

    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 1032, Column 175: reference to external entity in attribute value
    …12395&view=EventDetails&information_id=38082" style="border:0;">Distinguished …

    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 1032, Column 175: reference to entity "information_id" for which no system identifier could be generated
    …12395&view=EventDetails&information_id=38082" style="border:0;">Distinguished …

    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 640, Column 165: entity was defined here
    …ublic&eventidn=12398&view=EventDetails&information_id=38088"><img src="data1/i…
  • Error Line 1038, Column 49: document type does not allow element "td" here; assuming missing "tr" start-tag
    …                      <td valign="top"><div align="right" class="bluetext"><st…
  • Warning Line 1040, Column 94: reference not terminated by REFC delimiter
    …ventList.aspx?fromdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventi…

    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 1040, Column 94: reference to external entity in attribute value
    …ventList.aspx?fromdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventi…

    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 1040, Column 94: reference to entity "todate" for which no system identifier could be generated
    …ventList.aspx?fromdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventi…

    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 640, Column 89: entity was defined here
    …brook/EventList.aspx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=pub…
  • Warning Line 1040, Column 111: reference not terminated by REFC delimiter
    …mdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventidn=12353&view=Eve…

    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 1040, Column 111: reference to external entity in attribute value
    …mdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventidn=12353&view=Eve…

    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 1040, Column 111: reference to entity "display" for which no system identifier could be generated
    …mdate=2/1/2013&todate=2/1/2013&display=Day&type=public&eventidn=12353&view=Eve…

    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 640, Column 106: entity was defined here
    …spx?fromdate=2/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=1239…
  • Warning Line 1040, Column 120: reference not terminated by REFC delimiter
    …/2013&todate=2/1/2013&display=Day&type=public&eventidn=12353&view=EventDetails…

    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 1040, Column 120: reference to external entity in attribute value
    …/2013&todate=2/1/2013&display=Day&type=public&eventidn=12353&view=EventDetails…

    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 1040, Column 120: reference to entity "type" for which no system identifier could be generated
    …/2013&todate=2/1/2013&display=Day&type=public&eventidn=12353&view=EventDetails…

    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 640, Column 120: entity was defined here
    …/1/2013&todate=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDe…
  • Warning Line 1040, Column 136: reference not terminated by REFC delimiter
    …/2013&display=Day&type=public&eventidn=12353&view=EventDetails&information_id=…

    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 1040, Column 136: reference to external entity in attribute value
    …/2013&display=Day&type=public&eventidn=12353&view=EventDetails&information_id=…

    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 1040, Column 136: reference to entity "eventidn" for which no system identifier could be generated
    …/2013&display=Day&type=public&eventidn=12353&view=EventDetails&information_id=…

    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 640, Column 132: entity was defined here
    …te=2/28/2013&display=Month&type=public&eventidn=12398&view=EventDetails&inform…
  • Warning Line 1040, Column 147: reference not terminated by REFC delimiter
    …ay=Day&type=public&eventidn=12353&view=EventDetails&information_id=37983" styl…

    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 1040, Column 147: reference to external entity in attribute value
    …ay=Day&type=public&eventidn=12353&view=EventDetails&information_id=37983" styl…

    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 1040, Column 147: reference to entity "view" for which no system identifier could be generated
    …ay=Day&type=public&eventidn=12353&view=EventDetails&information_id=37983" styl…

    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 640, Column 147: entity was defined here
    …splay=Month&type=public&eventidn=12398&view=EventDetails&information_id=38088"…
  • Warning Line 1040, Column 175: reference not terminated by REFC delimiter
    …12353&view=EventDetails&information_id=37983" style="border:0;">Gilbert Kalish…

    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 1040, Column 175: reference to external entity in attribute value
    …12353&view=EventDetails&information_id=37983" style="border:0;">Gilbert Kalish…

    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 1040, Column 175: reference to entity "information_id" for which no system identifier could be generated
    …12353&view=EventDetails&information_id=37983" style="border:0;">Gilbert Kalish…

    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 640, Column 165: entity was defined here
    …ublic&eventidn=12398&view=EventDetails&information_id=38088"><img src="data1/i…
  • Error Line 1395, Column 92: required attribute "alt" not specified
    … shape="rect" coords="13,23,83,112" href="http://www.stonybrook.edu/connect" />

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

Visitor Analysis

Daily Visitor
  • 8.283 visits
Daily Visitor