Javascript is turned off in your web browser. Turn it on to take full advantage of this site, then refresh the page. Immigration & Checkpoints Authority Singapore Government -A A A+ Careers Sitemap ...

ica.gov.sg
  • Domain Name
    ica.gov.sg
  • Favicon
  • Google Page Rank
    7
  • Alexa Rank
    #31429
  • Page Size
    60.7 KB
  • Ip Address
    160.96.1.50
  • Heading
    H1: 0, H2: 4, H3: 3, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 3 JPG, 2 PNG

Website Meta Analysis

  • Title
    ICA - Immigration & Checkpoints Authority of Singapore
  • Meta Keyword
  • Meta Description
    Javascript is turned off in your web browser. Turn it on to take full advantage of this site, then refresh the page. Immigration & Checkpoints Authority Singapore Government -A A A+ Careers Sitemap Feedback Contact Info Home About ICA About ...

Technical Analysis

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

Hyper Text Transfer Protocol (HTTP) header show data header response from ica.gov.sg.

HTML Analysis

  • cache-control: public, max-age=294
  • date: Wed, 13 Feb 2013 18:16:16 GMT
  • content-type: text/html; charset=utf-8
  • expires: Wed, 13 Feb 2013 18:21:10 GMT
  • last-modified: Wed, 13 Feb 2013 18:06:10 GMT
  • vary: Accept-Encoding
  • x-powered-by: ASP.NET
  • x-aspnet-version: 2.0.50727
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

----------------------------------------------------------------------
SGNIC WHOIS Server
----------------------------------------------------------------------

The following data is provided for information purposes only.

Registrar: IDA

Domain Name: ICA.GOV.SG
Creation Date: 13-Jan-2003 11:05:16
Modified Date: 30-Nov-2008 01:01:35
Expiration Date: 13-Jan-2013 00:00:00
Domain Status: OK


Registrant:

Name: IMMIGRATION AND CHECKPOINTS AUTHORITY (SGNIC-ORGIM225028)



Administrative Contact:

Name: ALVIN TAN CHEE YEE (SGNIC-PER20004282)



Technical Contact:

Name: ALVIN TAN CHEE YEE (SGNIC-PER20004282)
Email: email



Name Servers:
PRIDNS.GOV.SG (160.96.179.4)
SECDNS.GOV.SG (160.96.179.134)












DNS Analysis


DNS servers
pridns.gov.sg [160.96.179.4]
secdns.gov.sg [160.96.179.134]

DNS Records

Answer records
ica.gov.sg SOA
server: pridns.gov.sg
email: root@pridns.gov.sg
serial: 2012121300
refresh: 28800
retry: 3600
expire: 4838400
minimum ttl: 14400
14400s
ica.gov.sg NS  pridns.gov.sg 14400s
ica.gov.sg NS  secdns.gov.sg 14400s
ica.gov.sg NS  extdns.dns3.gov.sg 14400s
ica.gov.sg MX
preference: 5
exchange: mailkdh2.email.gov.sg
14400s
ica.gov.sg MX
preference: 5
exchange: mailctp1.email.gov.sg
14400s
ica.gov.sg MX
preference: 5
exchange: mailctp2.email.gov.sg
14400s
ica.gov.sg MX
preference: 5
exchange: mailkdh1.email.gov.sg
14400s
ica.gov.sg A 160.96.1.50 14400s
ica.gov.sg TXT v=spf1 ip4:160.96.65.1 ip4:160.96.65.2 ip4:160.96.66.1 ip4:160.96.210.33 ip4:160.96.210.34 ip4:160.96.208.33 ip4:160.96.208.34 ip4:160.96.208.38 ip4:160.96.210.38 ?all 14400s

Authority records

Additional records
extdns.dns3.gov.sg A 203.125.49.10 14400s
pridns.gov.sg A 160.96.179.4 14400s
secdns.gov.sg A 160.96.179.134 14400s
mailctp1.email.gov.sg A 160.96.210.33 14400s

IP 160.96.1.50 Analysis

  • Country Code
    SG
  • Country Code3
    SGP
  • Country Name
    Singapore
  • City
    Singapore
  • Continent Code
    AS
  • Latitude
    1.2931
  • Longitude
    103.8558
  • % [whois.apnic.net node-5]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 160.96.0.0 - 160.96.255.255
    netname: IDA-SG
    descr: imported inetnum object for IDA Singapore
    country: SG
    admin-c: ISA3-AP
    tech-c: ISA3-AP
    status: ALLOCATED PORTABLE
    remarks: ----------
    remarks: imported from ARIN object:
    remarks:
    remarks: inetnum: 160.96.0.0 - 160.96.255.255
    remarks: netname: NCB-SGNET
    remarks: org-id: NCB-5
    remarks: status: assignment
    remarks: rev-srv: PRIDNS.GOV.SG
    SECDNS.GOV.SG
    remarks: tech-c: MTW15-ARIN
    remarks: reg-date: 1992-05-05
    remarks: changed: hostmaster@arin.net 19980323
    remarks: source: ARIN
    remarks:
    remarks: ----------
    notify: ida_sgnet_admin@ida.gov.sg
    mnt-by: APNIC-HM
    changed: hostmaster@arin.net 19980323
    changed: hm-changed@apnic.net 20040926
    changed: hm-changed@apnic.net 20040319
    changed: hm-changed@apnic.net 20040322
    changed: hm-changed@apnic.net 20041214
    source: APNIC

    person: IDA SGNET Admin
    address: 8 Temasek Boulevard #14-00
    address: Suntec Tower Three
    address: Singapore 038988
    country: SG
    phone: +65-6211-0888
    e-mail: ida_sgnet_admin@ida.gov.sg
    nic-hdl: ISA3-AP
    mnt-by: MAINT-NEW
    changed: hm-changed@apnic.net 20040322
    source: APNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 58 Errors
  • 44 Warnings
Ratio Text/Html
  • 0.6171259526029775
Message Error
  • Warning Line 7, Column 27: character "&" is the first character of a delimiter but occurred as data
    <title>ICA -  Immigration & Checkpoints Authority of Singapore</title> 

    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 8, Column 45: character "&" is the first character of a delimiter but occurred as data
    …name="DC.title" content=" Immigration & Checkpoints Authority of Singapore" />…

    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 38, Column 186: character "<" is the first character of a delimiter but occurred as data
    …utQuad:function(x,t,b,c,d){if((t/=d/2)<1)return c/2*t*t+b;return-c/2*((--t)*(t…

    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 38, Column 403: character "<" is the first character of a delimiter but occurred as data
    …tCubic:function(x,t,b,c,d){if((t/=d/2)<1)return c/2*t*t*t+b;return c/2*((t-=2)…

    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 38, Column 625: character "<" is the first character of a delimiter but occurred as data
    …tQuart:function(x,t,b,c,d){if((t/=d/2)<1)return c/2*t*t*t*t+b;return-c/2*((t-=…

    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 38, Column 855: character "<" is the first character of a delimiter but occurred as data
    …tQuint:function(x,t,b,c,d){if((t/=d/2)<1)return c/2*t*t*t*t*t+b;return c/2*((t…

    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 38, Column 1369: character "<" is the first character of a delimiter but occurred as data
    …eturn b;if(t==d)return b+c;if((t/=d/2)<1)return c/2*Math.pow(2,10*(t-1))+b;ret…

    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 38, Column 1631: character "<" is the first character of a delimiter but occurred as data
    …utCirc:function(x,t,b,c,d){if((t/=d/2)<1)return-c/2*(Math.sqrt(1-t*t)-1)+b;ret…

    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 38, Column 1840: character "(" not allowed in attribute specification list
    …)return b+c;if(!p)p=d*.3;if(a<Math.abs(c)){a=c;var s=p/4;}else var s=p/(2*Math…
  • Error Line 38, Column 1840: element "Math.abs" undefined
    …)return b+c;if(!p)p=d*.3;if(a<Math.abs(c)){a=c;var s=p/4;}else var s=p/(2*Math…

    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 38, Column 2101: character "(" not allowed in attribute specification list
    …)return b+c;if(!p)p=d*.3;if(a<Math.abs(c)){a=c;var s=p/4;}else var s=p/(2*Math…
  • Error Line 38, Column 2101: element "Math.abs" undefined
    …)return b+c;if(!p)p=d*.3;if(a<Math.abs(c)){a=c;var s=p/4;}else var s=p/(2*Math…

    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 38, Column 2368: character "(" not allowed in attribute specification list
    …n b+c;if(!p)p=d*(.3*1.5);if(a<Math.abs(c)){a=c;var s=p/4;}else var s=p/(2*Math…
  • Error Line 38, Column 2368: element "Math.abs" undefined
    …n b+c;if(!p)p=d*(.3*1.5);if(a<Math.abs(c)){a=c;var s=p/4;}else var s=p/(2*Math…

    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 38, Column 2432: character "<" is the first character of a delimiter but occurred as data
    …ar s=p/(2*Math.PI)*Math.asin(c/a);if(t<1)return-.5*(a*Math.pow(2,10*(t-=1))*Ma…

    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 38, Column 2845: character "<" is the first character of a delimiter but occurred as data
    …{if(s==undefined)s=1.70158;if((t/=d/2)<1)return c/2*(t*t*(((s*=(1.525))+1)*t-s…

    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 38, Column 3071: character "<" is the first character of a delimiter but occurred as data
    …utBounce:function(x,t,b,c,d){if((t/=d)<(1/2.75)){return c*(7.5625*t*t)+b;}else…

    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 38, Column 3116: character "<" is the first character of a delimiter but occurred as data
    …5)){return c*(7.5625*t*t)+b;}else if(t<(2/2.75)){return c*(7.5625*(t-=(1.5/2.7…

    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 38, Column 3179: character "<" is the first character of a delimiter but occurred as data
    …25*(t-=(1.5/2.75))*t+.75)+b;}else if(t<(2.5/2.75)){return c*(7.5625*(t-=(2.25/…

    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 38, Column 3337: NET-enabling start-tag not immediately followed by null end-tag
    …nOutBounce:function(x,t,b,c,d){if(t<d/2)return jQuery.easing.easeInBounce(x,t*…

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

  • Error Line 38, Column 3337: element "d" undefined
    …nOutBounce:function(x,t,b,c,d){if(t<d/2)return jQuery.easing.easeInBounce(x,t*…

    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 39, Column 1063: character "&" is the first character of a delimiter but occurred as data
    …g);});}if((base.options.hashTags==true&&!base.gotoHash())||base.options.hashTa…

    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 39, Column 1064: character "&" is the first character of a delimiter but occurred as data
    …);});}if((base.options.hashTags==true&&!base.gotoHash())||base.options.hashTag…

    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 39, Column 1366: character "<" is the first character of a delimiter but occurred as data
    …e>base.pages+1)page=base.pages;if(page<0)page=1;var dir=page<base.currentPage?…

    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 39, Column 1405: character "?" not allowed in attribute specification list
    …0)page=1;var dir=page<base.currentPage?-1:1,n=Math.abs(base.currentPage-page),…
  • Error Line 39, Column 1405: element "base.currentPage" undefined
    …0)page=1;var dir=page<base.currentPage?-1:1,n=Math.abs(base.currentPage-page),…

    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 67, Column 13: end tag for "base.currentPage" 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 39, Column 1388: start tag was here
    …se.pages;if(page<0)page=1;var dir=page<base.currentPage?-1:1,n=Math.abs(base.c…
  • Error Line 67, Column 13: end tag for "Math.abs" 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 38, Column 2359: start tag was here
    …==2)return b+c;if(!p)p=d*(.3*1.5);if(a<Math.abs(c)){a=c;var s=p/4;}else var s=…
  • Error Line 67, Column 13: end tag for "Math.abs" 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 38, Column 2092: start tag was here
    …(t/=d)==1)return b+c;if(!p)p=d*.3;if(a<Math.abs(c)){a=c;var s=p/4;}else var s=…
  • Error Line 67, Column 13: end tag for "Math.abs" 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 38, Column 1831: start tag was here
    …(t/=d)==1)return b+c;if(!p)p=d*.3;if(a<Math.abs(c)){a=c;var s=p/4;}else var s=…
  • Warning Line 130, Column 318: character "&" is the first character of a delimiter but occurred as data
    …aspx?pageid=66' target='_self'>Vision & Mission</a></li><li><a href='/page.asp…

    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 130, Column 610: character "&" is the first character of a delimiter but occurred as data
    …target='_self'>History of Immigration & Checkpoints Authority (ICA)</a></li><l…

    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 130, Column 773: character "&" is the first character of a delimiter but occurred as data
    …01' target='_self'>History of Customs & Excise Department (CED)</a><ul><li><a …

    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 130, Column 1334: character "&" is the first character of a delimiter but occurred as data
    …elf'>History of Singapore Immigration & Registration</a><ul><li><a href='/page…

    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 130, Column 1440: character "&" is the first character of a delimiter but occurred as data
    …elf'>History of Singapore Immigration & Registration (SIR)</a></li><li><a href…

    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 130, Column 1743: character "&" is the first character of a delimiter but occurred as data
    …t='_self'>History of Travel Documents & Passes</a></li><li><a href='/page.aspx…

    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 130, Column 3243: character "&" is the first character of a delimiter but occurred as data
    … target='_self'>Home Affairs Learning & Growth (HALO) Programme</a></li></ul><…

    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 130, Column 3721: character "&" is the first character of a delimiter but occurred as data
    …pageid=330' target='_self'>Prohibited & Controlled Items</a></li><li><a href='…

    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 130, Column 4048: character "&" is the first character of a delimiter but occurred as data
    …?pageid=313' target='_self'>eServices & Forms</a><ul><li><a href='/e_services.…

    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 130, Column 4138: character "&" is the first character of a delimiter but occurred as data
    …313' target='_self'>List of eServices & Forms</a></li><li><a href='/e_services…

    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 130, Column 9707: character "&" is the first character of a delimiter but occurred as data
    …aspx?pageid=369' target='_self'>Birth & Death Statistics</a></li></ul></li><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 206, Column 47: document type does not allow element "div" here; assuming missing "li" start-tag
                        <div style="display:block">
  • Error Line 207, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="/page.aspx?pageid=125&amp;secid=122" shape…

    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 211, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="http://www.ica.gov.sg/page.aspx?pageid=137…

    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 215, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="http://www.ica.gov.sg/page.aspx?pageid=75&…

    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 219, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="http://www.ica.gov.sg/page.aspx?pageid=128…

    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 223, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="/services_centre_overview.aspx?pageid=246&…

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

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

  • Info Line 206, Column 21: start tag was here
                        <div style="display:block">
  • Error Line 238, Column 47: document type does not allow element "div" here; assuming missing "li" start-tag
                        <div style="display:block">
  • Error Line 239, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="/page.aspx?pageid=151&amp;secid=150" targe…

    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 243, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="/page.aspx?pageid=154&amp;secid=153" targe…

    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 247, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="/page.aspx?pageid=156&amp;secid=153" targe…

    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 251, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="/services_centre_overview.aspx?pageid=250&…

    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 255, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="/page.aspx?pageid=152&amp;secid=150" targe…

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

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

  • Info Line 238, Column 21: start tag was here
                        <div style="display:block">
  • Error Line 270, Column 47: document type does not allow element "div" here; assuming missing "li" start-tag
                        <div style="display:block">
  • Error Line 271, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="/services_centre_overview.aspx?pageid=252&…

    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 275, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="http://www.ica.gov.sg/services_centre_over…

    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 279, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="http://www.ica.gov.sg/services_centre_over…

    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 283, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="/services_centre_overview.aspx?pageid=256&…

    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 287, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="http://www.ica.gov.sg/services_centre_over…

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

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

  • Info Line 270, Column 21: start tag was here
                        <div style="display:block">
  • Warning Line 305, Column 48: cannot generate system identifier for general entity "secid"
    …       <a href="/page.aspx?pageid=344&secid=1" target="_blank"><img src="/data…

    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 305, Column 48: general entity "secid" not defined and no default entity
    …       <a href="/page.aspx?pageid=344&secid=1" target="_blank"><img src="/data…

    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 305, Column 53: reference not terminated by REFC delimiter
    …  <a href="/page.aspx?pageid=344&secid=1" target="_blank"><img src="/data//ima…

    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 305, Column 53: reference to external entity in attribute value
    …  <a href="/page.aspx?pageid=344&secid=1" target="_blank"><img src="/data//ima…

    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 305, Column 53: reference to entity "secid" for which no system identifier could be generated
    …  <a href="/page.aspx?pageid=344&secid=1" target="_blank"><img src="/data//ima…

    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 305, Column 47: entity was defined here
    …        <a href="/page.aspx?pageid=344&secid=1" target="_blank"><img src="/dat…
  • Error Line 338, Column 32: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p style="margin: 0cm 0cm 0pt;"><span style="font-size: 16px; font-family: cali…

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

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

  • Warning Line 364, Column 86: cannot generate system identifier for general entity "isNew"
    …App/tmf/TMFServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">…

    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 364, Column 86: general entity "isNew" not defined and no default entity
    …App/tmf/TMFServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">…

    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 364, Column 91: reference not terminated by REFC delimiter
    …mf/TMFServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passp…

    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 364, Column 91: reference to external entity in attribute value
    …mf/TMFServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passp…

    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 364, Column 91: reference to entity "isNew" for which no system identifier could be generated
    …mf/TMFServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passp…

    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 364, Column 85: entity was defined here
    …SApp/tmf/TMFServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank"…
  • Warning Line 364, Column 97: cannot generate system identifier for general entity "Reload"
    …Servlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passport (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 364, Column 97: general entity "Reload" not defined and no default entity
    …Servlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passport (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 364, Column 103: reference not terminated by REFC delimiter
    …t?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passport (APPLES)…

    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 364, Column 103: reference to external entity in attribute value
    …t?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passport (APPLES)…

    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 364, Column 103: reference to entity "Reload" for which no system identifier could be generated
    …t?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passport (APPLES)…

    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 364, Column 96: entity was defined here
    …FServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passport (…
  • Warning Line 372, Column 89: reference not terminated by REFC delimiter
    …/tmf/TMFServlet?app=STSVP-PUBLIC&isNew=true&Reload=true" target="_blank">Exten…

    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 372, Column 89: reference to external entity in attribute value
    …/tmf/TMFServlet?app=STSVP-PUBLIC&isNew=true&Reload=true" target="_blank">Exten…

    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 372, Column 89: reference to entity "isNew" for which no system identifier could be generated
    …/tmf/TMFServlet?app=STSVP-PUBLIC&isNew=true&Reload=true" target="_blank">Exten…

    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 364, Column 85: entity was defined here
    …SApp/tmf/TMFServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank"…
  • Warning Line 372, Column 101: reference not terminated by REFC delimiter
    …let?app=STSVP-PUBLIC&isNew=true&Reload=true" target="_blank">Extension of Shor…

    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 372, Column 101: reference to external entity in attribute value
    …let?app=STSVP-PUBLIC&isNew=true&Reload=true" target="_blank">Extension of Shor…

    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 372, Column 101: reference to entity "Reload" for which no system identifier could be generated
    …let?app=STSVP-PUBLIC&isNew=true&Reload=true" target="_blank">Extension of Shor…

    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 364, Column 96: entity was defined here
    …FServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passport (…
  • Warning Line 376, Column 86: reference not terminated by REFC delimiter
    …App/tmf/TMFServlet?app=SAVE-OVAL&isNew=true&Reload=true" target="_blank">Visa …

    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 376, Column 86: reference to external entity in attribute value
    …App/tmf/TMFServlet?app=SAVE-OVAL&isNew=true&Reload=true" target="_blank">Visa …

    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 376, Column 86: reference to entity "isNew" for which no system identifier could be generated
    …App/tmf/TMFServlet?app=SAVE-OVAL&isNew=true&Reload=true" target="_blank">Visa …

    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 364, Column 85: entity was defined here
    …SApp/tmf/TMFServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank"…
  • Warning Line 376, Column 98: reference not terminated by REFC delimiter
    …ervlet?app=SAVE-OVAL&isNew=true&Reload=true" target="_blank">Visa (SAVE)</a></…

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

  • Warning Line 376, Column 98: reference to external entity in attribute value
    …ervlet?app=SAVE-OVAL&isNew=true&Reload=true" target="_blank">Visa (SAVE)</a></…

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

  • Error Line 376, Column 98: reference to entity "Reload" for which no system identifier could be generated
    …ervlet?app=SAVE-OVAL&isNew=true&Reload=true" target="_blank">Visa (SAVE)</a></…

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

  • Info Line 364, Column 96: entity was defined here
    …FServlet?app=MHA-SIR-APPLES&isNew=true&Reload=true" target="_blank">Passport (…
  • Error Line 399, Column 35: document type does not allow element "div" here; assuming missing "li" start-tag
    				    <div style="display:block">
  • Error Line 400, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="http://www.ica.gov.sg/page.aspx?pageid=64&…

    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 401, Column 3: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    <p>About ICA</p></a></li>

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

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

  • Error Line 405, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="http://www.ica.gov.sg/page.aspx?pageid=95&…

    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 409, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="/page.aspx?pageid=144&amp;secid=143" targe…

    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 413, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="http://www.ica.gov.sg/page.aspx?pageid=137…

    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 417, Column 28: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
                            <li><a href="http://www.ica.gov.sg/page.aspx?pageid=117…

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

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

  • Info Line 399, Column 9: start tag was here
    				    <div style="display:block">
  • Error Line 463, Column 31: character ";" not allowed in attribute specification list
            for (i=0; i<frm.length; i++) 
  • Error Line 463, Column 31: element "frm.length" undefined
            for (i=0; i<frm.length; i++) 

    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 478, Column 9: end tag for "frm.length" 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 463, Column 20: start tag was here
            for (i=0; i<frm.length; i++) 
  • Error Line 615, Column 19: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
        <li id="trust"><a href="https://www.trustsg.com/" title="TrustSg" target="_…

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

Visitor Analysis

Daily Visitor
  • 7.467 visits
Daily Visitor