irishrail.ie

Use the website to buy train tickets, reserve seats, check train times, destinations, new trains and information useful for your rail journey ...

Display Widget for this domain on your website. Click Here
This data was last updated from 25-06-2013 09:52:40  (update).

Overview Info

  • Domain Name
    irishrail.ie
  • Favicon
  • Alexa Rank
    #56842
  • Google Page Rank
    PR 8
  • Ip Address
    194.106.151.77
  • Page Size
    32.3 KB
  • Images
    4 GIF, 5 JPG, 20 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    5 1 5 0 0 0

Website Meta Analysis



  • Title
    Ireland rail travel information - Iarnród Éireann - Irish Rail
  • Meta Keyword
    Irish Rail, Iarnrod Eireann, Ireland, train times, train tickets, buy online, discounted, rail tickets, train timetables, train fares, value fares, great deals, special offers, ticket types, railway, rail, stations, travel, city gold, DART, Rosslare Harbour
  • Meta Description
    Use the website to buy train tickets, reserve seats, check train times, destinations, new trains and information useful for your rail journey

Technical Analysis



  • Webserver
  • Ip Address
    194.106.151.77
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from irishrail.ie.

HTML Analysis

  • content-length: 31434
  • content-type: text/html
  • last-modified: Tue, 25 Jun 2013 21:51:27 GMT
  • accept-ranges: bytes
  • etag: W/"31434-1372197087322"
  • server:
  • date: Tue, 25 Jun 2013 21:52:37 GMT
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for irishrail.ie

DNS Analysis


DNS servers
auth03.ns.eircom.net [159.134.191.34]
auth01.ns.eircom.net [159.134.237.61]
auth02.ns.eircom.net [159.134.237.59]


DNS Records

Answer records
irishrail.ie SOA
server: auth01.ns.eircom.net
email: hostmaster@eircom.net
serial: 2012111501
refresh: 28800
retry: 7200
expire: 604800
minimum ttl: 86400
86400s
irishrail.ie TXT v=spf1 mx -all 86400s
irishrail.ie TXT Coras Iompair Eireann CIE 86400s
irishrail.ie NS  auth03.ns.eircom.net 86400s
irishrail.ie NS  auth02.ns.eircom.net 86400s
irishrail.ie NS  auth01.ns.eircom.net 86400s
irishrail.ie MX
preference: 5
exchange: mailgate4.cie.ie
86400s
irishrail.ie MX
preference: 100
exchange: mailgate5.cie.ie
86400s
irishrail.ie A 194.106.151.77 86400s

Authority records

Additional records
auth01.ns.eircom.net A 159.134.237.61 86400s
auth02.ns.eircom.net A 159.134.237.59 86400s
auth03.ns.eircom.net A 159.134.191.34 86400s
mailgate4.cie.ie A 194.106.151.4 86400s
mailgate5.cie.ie A 194.106.151.5 86400s

IP 194.106.151.77 Analysis

  • Country Code
    IE
  • Country Code3
    IRL
  • Country Name
    Ireland
  • City
    EU
  • Continent Code
    53° North
  • Latitude
    8.
  • Longitude
  • No whois ip data for 194.106.151.77

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 73 Errors
  • 13 Warnings
Ratio Text/Html
  • 0.8092632342715482
Message Error
  • Error Line 13, Column 16: there is no attribute "property"
    <meta property="fb:page_id" content="166535193895" />

    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 68, Column 102: there is no attribute "onClick"
    …ge to the main content area"  onClick="_gaq.push(['_trackEvent', 'Internal Lin…

    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 102, Column 18: there is no attribute "language"
    <script language="javascript" type="text/javascript">

    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 103, Column 38: an attribute value must be a literal unless it contains only name characters
            document.write("<form action=\"http://www.irishrail.ie/site_search.jsp\…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 103, Column 89: an attribute value must be a literal unless it contains only name characters
    …irishrail.ie/site_search.jsp\" method=\"get\" name=\"searchform\" class=\"frmS…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 103, Column 89: character "\" is not allowed in the value of attribute "method"
    …irishrail.ie/site_search.jsp\" method=\"get\" name=\"searchform\" class=\"frmS…

    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.

  • Error Line 103, Column 89: value of attribute "method" cannot be "\"get\""; must be one of "get", "post"
    …irishrail.ie/site_search.jsp\" method=\"get\" name=\"searchform\" class=\"frmS…

    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 103, Column 102: there is no attribute "name"
    …site_search.jsp\" method=\"get\" name=\"searchform\" class=\"frmSearch\" onsub…

    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 103, Column 102: an attribute value must be a literal unless it contains only name characters
    …site_search.jsp\" method=\"get\" name=\"searchform\" class=\"frmSearch\" onsub…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 103, Column 123: an attribute value must be a literal unless it contains only name characters
    …hod=\"get\" name=\"searchform\" class=\"frmSearch\" onsubmit=\"return validate…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 103, Column 146: an attribute value must be a literal unless it contains only name characters
    …ame=\"searchform\" class=\"frmSearch\" onsubmit=\"return validateSearch()\">");

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 103, Column 169: "validateSearch" is not a member of a group specified for any attribute
    …ame=\"searchform\" class=\"frmSearch\" onsubmit=\"return validateSearch()\">");
  • Error Line 103, Column 173: document type does not allow element "form" here
    …ame=\"searchform\" class=\"frmSearch\" onsubmit=\"return validateSearch()\">");

    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 103, Column 174: character data is not allowed here
    …ame=\"searchform\" class=\"frmSearch\" onsubmit=\"return validateSearch()\">");

    You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

    • putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
    • forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
    • using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
  • Error Line 104, Column 54: an attribute value must be a literal unless it contains only name characters
    …t.write("<fieldset><ol><li><label for=\"search_term\">Enter search term or key…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 104, Column 54: character "\" is not allowed in the value of attribute "for"
    …t.write("<fieldset><ol><li><label for=\"search_term\">Enter search term or key…

    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 104, Column 99: character "<" is the first character of a delimiter but occurred as data
    …et><ol><li><label for=\"search_term\">Enter search term or keyword:<\/label>");

    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 105, Column 31: an attribute value must be a literal unless it contains only name characters
    		document.write("<input type=\"text\" id=\"search_term\" name=\"search_term\" …

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 105, Column 31: character "\" is not allowed in the value of attribute "type"
    		document.write("<input type=\"text\" id=\"search_term\" name=\"search_term\" …

    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.

  • Error Line 105, Column 31: value of attribute "type" cannot be "\"text\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    		document.write("<input type=\"text\" id=\"search_term\" name=\"search_term\" …

    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 105, Column 43: an attribute value must be a literal unless it contains only name characters
    …cument.write("<input type=\"text\" id=\"search_term\" name=\"search_term\" val…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 105, Column 43: character "\" is not allowed in the value of attribute "id"
    …cument.write("<input type=\"text\" id=\"search_term\" name=\"search_term\" val…

    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.

  • Error Line 105, Column 64: an attribute value must be a literal unless it contains only name characters
    …type=\"text\" id=\"search_term\" name=\"search_term\" value=\"Search Site\" on…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 105, Column 86: an attribute value must be a literal unless it contains only name characters
    …rch_term\" name=\"search_term\" value=\"Search Site\" onfocus=\"if(this.value=…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 105, Column 99: "Site" is not a member of a group specified for any attribute
    …me=\"search_term\" value=\"Search Site\" onfocus=\"if(this.value=='Search Site…
  • Error Line 105, Column 110: an attribute value must be a literal unless it contains only name characters
    …_term\" value=\"Search Site\" onfocus=\"if(this.value=='Search Site')this.valu…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 105, Column 139: an attribute value literal can occur in an attribute specification list only after a VI delimiter
    … onfocus=\"if(this.value=='Search Site')this.value='';\" onblur=\"if(this.valu…

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

  • Error Line 105, Column 140: end tag for "input" omitted, but OMITTAG NO was specified
    …onfocus=\"if(this.value=='Search Site')this.value='';\" onblur=\"if(this.value…

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

  • Info Line 105, Column 19: start tag was here
    		document.write("<input type=\"text\" id=\"search_term\" name=\"search_term\" …
  • Error Line 106, Column 31: an attribute value must be a literal unless it contains only name characters
    		document.write("<input type=\"image\" src=\"images/btn_search.gif\" alt=\"Sea…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 106, Column 31: character "\" is not allowed in the value of attribute "type"
    		document.write("<input type=\"image\" src=\"images/btn_search.gif\" alt=\"Sea…

    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.

  • Error Line 106, Column 31: value of attribute "type" cannot be "\"image\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
    		document.write("<input type=\"image\" src=\"images/btn_search.gif\" alt=\"Sea…

    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 106, Column 45: an attribute value must be a literal unless it contains only name characters
    …ment.write("<input type=\"image\" src=\"images/btn_search.gif\" alt=\"Search\"…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 106, Column 75: an attribute value must be a literal unless it contains only name characters
    …e\" src=\"images/btn_search.gif\" alt=\"Search\" title=\"Search\" class=\"btn\…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 106, Column 92: an attribute value must be a literal unless it contains only name characters
    …btn_search.gif\" alt=\"Search\" title=\"Search\" class=\"btn\" />");		document…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 106, Column 109: an attribute value must be a literal unless it contains only name characters
    …alt=\"Search\" title=\"Search\" class=\"btn\" />");		document.write("<\/li><\/…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Warning Line 106, Column 140: character "<" is the first character of a delimiter but occurred as data
    …tle=\"Search\" class=\"btn\" />");		document.write("<\/li><\/ol><\/fieldset>");

    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 106, Column 146: character "<" is the first character of a delimiter but occurred as data
    …tle=\"Search\" class=\"btn\" />");		document.write("<\/li><\/ol><\/fieldset>");

    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 106, Column 152: character "<" is the first character of a delimiter but occurred as data
    …tle=\"Search\" class=\"btn\" />");		document.write("<\/li><\/ol><\/fieldset>");

    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 107, Column 26: character "<" is the first character of a delimiter but occurred as data
            document.write(" <\/form>");

    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 108, Column 9: end tag for "label" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 104, Column 43: start tag was here
    …    document.write("<fieldset><ol><li><label for=\"search_term\">Enter search …
  • Error Line 108, Column 9: end tag for "li" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 104, Column 39: start tag was here
            document.write("<fieldset><ol><li><label for=\"search_term\">Enter sear…
  • Error Line 108, Column 9: end tag for "ol" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 104, Column 35: start tag was here
            document.write("<fieldset><ol><li><label for=\"search_term\">Enter sear…
  • Error Line 108, Column 9: end tag for "fieldset" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 104, Column 25: start tag was here
            document.write("<fieldset><ol><li><label for=\"search_term\">Enter sear…
  • Error Line 108, Column 9: end tag for "form" omitted, but OMITTAG NO was specified
    </script>

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

  • Info Line 103, Column 25: start tag was here
            document.write("<form action=\"http://www.irishrail.ie/site_search.jsp\…
  • Error Line 111, Column 198: there is no attribute "target"
    …="Follow Irishrail on twitter" target="_blank"><img alt="Follow Irish Rail on …

    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 126, Column 52: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="timesel" value="arrive"/>

    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 127, Column 46: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="start" value="1" />

    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 128, Column 76: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="REQ0JourneyDate" id="REQ0JourneyDate" value="" />

    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 129, Column 76: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="REQ0JourneyTime" id="REQ0JourneyTime" value="" />

    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 130, Column 92: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …hidden" name="REQ0HafasPeriodToSearch" id="REQ0HafasPeriodToSearch" value="" />

    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 89: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …e="hidden" name="REQ0HafasPeriodSearch" id="REQ0HafasPeriodSearch" value="2" />

    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 132, Column 85: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    … type="hidden" name="REQ0HafasSearchForw" id="REQ0HafasSearchForw" value="1" />

    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 133, Column 85: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    … type="hidden" name="special_search_both" id="special_search_both" value="0" />

    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 134, Column 76: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="REQ1JourneyDate" id="REQ1JourneyDate" value="" />

    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 135, Column 76: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <input type="hidden" name="REQ1JourneyTime" id="REQ1JourneyTime" value="" />

    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 136, Column 96: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …en" name="REQ1HafasPeriodToSearch" id="REQ1HafasPeriodToSearch" value="1440" />

    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 137, Column 89: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …e="hidden" name="REQ1HafasPeriodSearch" id="REQ1HafasPeriodSearch" value="2" />

    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 138, Column 85: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    … type="hidden" name="REQ1HafasSearchForw" id="REQ1HafasSearchForw" value="0" />

    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 194, Column 33: an attribute value must be a literal unless it contains only name characters
        document.write("<input type=\"image\" src=\"images/booking/btn-go.png\" alt…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 194, Column 33: character "\" is not allowed in the value of attribute "type"
        document.write("<input type=\"image\" src=\"images/booking/btn-go.png\" alt…

    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.

  • Error Line 194, Column 33: value of attribute "type" cannot be "\"image\""; must be one of "text", "password", "checkbox", "radio", "submit", "reset", "file", "hidden", "image", "button"
        document.write("<input type=\"image\" src=\"images/booking/btn-go.png\" alt…

    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 194, Column 47: an attribute value must be a literal unless it contains only name characters
    …ment.write("<input type=\"image\" src=\"images/booking/btn-go.png\" alt=\"Go\"…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 194, Column 81: an attribute value must be a literal unless it contains only name characters
    …src=\"images/booking/btn-go.png\" alt=\"Go\" id=\"jpGo\" class=\"btn\" title=\…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 194, Column 91: an attribute value must be a literal unless it contains only name characters
    …es/booking/btn-go.png\" alt=\"Go\" id=\"jpGo\" class=\"btn\" title=\"Start req…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 194, Column 91: character "\" is not allowed in the value of attribute "id"
    …es/booking/btn-go.png\" alt=\"Go\" id=\"jpGo\" class=\"btn\" title=\"Start req…

    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.

  • Error Line 194, Column 106: an attribute value must be a literal unless it contains only name characters
    …btn-go.png\" alt=\"Go\" id=\"jpGo\" class=\"btn\" title=\"Start request\" />");

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 194, Column 120: an attribute value must be a literal unless it contains only name characters
    …btn-go.png\" alt=\"Go\" id=\"jpGo\" class=\"btn\" title=\"Start request\" />");

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 194, Column 135: "request" is not a member of a group specified for any attribute
    …btn-go.png\" alt=\"Go\" id=\"jpGo\" class=\"btn\" title=\"Start request\" />");
  • Error Line 194, Column 139: document type does not allow element "input" here
    …btn-go.png\" alt=\"Go\" id=\"jpGo\" class=\"btn\" title=\"Start request\" />");

    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 202, Column 20: document type does not allow element "br" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    <br class="clear" />

    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 217, Column 15: there is no attribute "value"
    <ul><li value="0"><img alt="You can't relax like this in your car" src="media/W…

    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 236, Column 64: cannot generate system identifier for general entity "n"
    …w-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></…

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

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

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

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

  • Error Line 236, Column 64: general entity "n" not defined and no default entity
    …w-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></…

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

  • Warning Line 236, Column 65: reference not terminated by REFC delimiter
    …-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></p…

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

  • Warning Line 236, Column 65: reference to external entity in attribute value
    …-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></p…

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

  • Error Line 236, Column 65: reference to entity "n" for which no system identifier could be generated
    …-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></p…

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

  • Info Line 236, Column 63: entity was defined here
    …ew-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a><…
  • Warning Line 236, Column 70: cannot generate system identifier for general entity "ci"
    …-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></p>

    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 236, Column 70: general entity "ci" not defined and no default entity
    …-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></p>

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

  • Warning Line 236, Column 72: reference not terminated by REFC delimiter
    …-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></p>

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

  • Warning Line 236, Column 72: reference to external entity in attribute value
    …-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></p>

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

  • Error Line 236, Column 72: reference to entity "ci" for which no system identifier could be generated
    …-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></p>

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

  • Info Line 236, Column 69: entity was defined here
    …-more"><a href="cat_offers.jsp?p=118&n=144&ci=4">View all latest offers</a></p>
  • Warning Line 350, Column 212: cannot generate system identifier for general entity "T"
    …nk" title="Visit the HaCon website">HaCon</a> / CIÉ GIT&T / Iarnród Éireann</p>

    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 350, Column 212: general entity "T" not defined and no default entity
    …nk" title="Visit the HaCon website">HaCon</a> / CIÉ GIT&T / Iarnród Éireann</p>

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

  • Warning Line 350, Column 213: reference not terminated by REFC delimiter
    …nk" title="Visit the HaCon website">HaCon</a> / CIÉ GIT&T / Iarnród Éireann</p>

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

  • Error Line 350, Column 213: reference to entity "T" for which no system identifier could be generated
    …nk" title="Visit the HaCon website">HaCon</a> / CIÉ GIT&T / Iarnród Éireann</p>

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

  • Info Line 350, Column 211: entity was defined here
    …nk" title="Visit the HaCon website">HaCon</a> / CIÉ GIT&T / Iarnród Éireann</p>

Visitor Analysis

Daily Visitor
  • 2.683 visits
Daily Visitor

In Page Analysis