F1.com F1 - The Official Home of Formula 1® Racing
Enter the world of Formula 1. Your go-to source for the latest F1 news, video highlights, GP results, live timing, in-depth analysis and expert commen...
Online Status
Online
Server IP address resolved: Yes
Http response code: 200
Response time: 0.17 sec.
Last Checked: 08/14/2023
F1.com receives about 14,007 unique visitors and 70,035 pageviews per day. The estimated value of f1.com is 105,000 USD. Each unique visitor makes about 5 pageviews on average.
F1.com is registered under .COM top-level domain. Check other websites in .COM zone.
At the time of the last check (August 14, 2024) f1.com has an expired SSL certificate issued by Let's Encrypt (expired on October 26, 2024). Check other websites using SSL certificates issued by Let's Encrypt.
According to Google Safe Browsing, Google Safe Search, Symantec and Web of Trust f1.com is quite a safe domain.
Mobile-Friendly test indicates that f1.com is well optimized for mobile and tablet devices, however website page loading time could be improved.
Not tested yet
Alexa Rank shows how popular f1.com is in comparison with other sites. The most popular site has Alexa Rank equals 1. If f1.com has Alexa Rank equals 100,000, then it is in TOP 100,000 popular sites in the world. The rank is calculated using a combination of average daily visitors to f1.com and pageviews on f1.com over the past 3 months.
Overview
Last Updated: 11/05/2024
Overall result - "f1.com" is SAFE.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton Connect Safe
Last Updated: 02/09/2024
f1.com is safe.
Norton ConnectSafe evaluates f1.com for any unsafe and insecure content. The results are critical for families with young children.
Google Safe Search
Last Updated: 10/07/2019
f1.com is safe.
SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.
Google Safe Browsing
Last Updated: 01/09/2019
Malware not found at "f1.com".
"f1.com" is not a phishing page.
"f1.com" does not install unwanted software.
"f1.com" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
"f1.com" is not a phishing page.
"f1.com" does not install unwanted software.
"f1.com" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
Site Advisor
Last Updated: 02/08/2021
f1.com is safe.
McAfee assesses f1.com for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze f1.com for mature or inappropriate content, only security checks are evaluated.
Web of Trust
Last Updated: 01/11/2019
f1.com child safety isvery good.
The WOT calculates reputation of the f1.com. This reputation system receives ratings from users and information from third-party sources, assesses the f1.com for safety features and confirms, whether f1.com is suitable for children.
SSL Information
| Domain | f1.com |
| Issuer Organization | Let's Encrypt |
| Issuer | R11 |
| Algorithm | RSA-SHA256 |
| Valid form | 07/28/2024 |
| Expiration | 10/26/2024 |
| Signed | Certificate is not self signed |
| Additional Domains | f1.com |
Server Location
New York City
New York
United States
ASN Information
ASN ID: 396982
ASN Title: GOOGLE-PRIVATE-CLOUD - Google LLC, US
Last Update: 03/04/2024
ASN Whois
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2019, American Registry for Internet Numbers, Ltd.
#
ASNumber: 396982
ASName: GOOGLE-PRIVATE-CLOUD
ASHandle: AS396982
RegDate: 2018-08-15
Updated: 2018-08-15
Comment: *** This ASN is used for Google Private Cloud ***
Comment:
Comment: Direct all copyright and legal complaints to
Comment: https://support.google.com/legal/go/report
Comment:
Comment: Direct all spam and abuse complaints to
Comment: https://support.google.com/code/go/gce_abuse_report
Comment:
Comment: For fastest response, use the relevant forms above.
Comment:
Comment: Complaints can also be sent to the GC Abuse desk
Comment: (google-cloud-compliance@google.com)
Comment: but may have longer turnaround times.
Comment:
Comment: Complaints sent to any other POC will be ignored.
Ref: https://rdap.arin.net/registry/autnum/396982
OrgName: Google LLC
OrgId: GOOGL-2
Address: 1600 Amphitheatre Parkway
City: Mountain View
StateProv: CA
PostalCode: 94043
Country: US
RegDate: 2006-09-29
Updated: 2017-12-21
Comment: *** The IP addresses under this Org-ID are in use by Google Cloud customers ***
Comment:
Comment: Direct all copyright and legal complaints to
Comment: https://support.google.com/legal/go/report
Comment:
Comment: Direct all spam and abuse complaints to
Comment: https://support.google.com/code/go/gce_abuse_report
Comment:
Comment: For fastest response, use the relevant forms above.
Comment:
Comment: Complaints can also be sent to the GC Abuse desk
Comment: (google-cloud-compliance@google.com)
Comment: but may have longer turnaround times.
Comment:
Comment: Complaints sent to any other POC will be ignored.
Ref: https://rdap.arin.net/registry/entity/GOOGL-2
OrgTechHandle: ZG39-ARIN
OrgTechName: Google LLC
OrgTechPhone: +1-650-253-0000
OrgTechEmail: arin-contact@google.com
OrgTechRef: https://rdap.arin.net/registry/entity/ZG39-ARIN
OrgAbuseHandle: GCABU-ARIN
OrgAbuseName: GC Abuse
OrgAbusePhone: +1-650-253-0000
OrgAbuseEmail: google-cloud-compliance@google.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/GCABU-ARIN
OrgNOCHandle: GCABU-ARIN
OrgNOCName: GC Abuse
OrgNOCPhone: +1-650-253-0000
OrgNOCEmail: google-cloud-compliance@google.com
OrgNOCRef: https://rdap.arin.net/registry/entity/GCABU-ARIN
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2019, American Registry for Internet Numbers, Ltd.
#
WHOIS
Domain Whois
Domain Name: F1.COM
Registry Domain ID: 1040834_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.comlaude.com
Registrar URL: http://www.comlaude.com
Updated Date: 2022-02-05T23:05:53Z
Creation Date: 1995-03-06T05:00:00Z
Registry Expiry Date: 2023-03-07T05:00:00Z
Registrar: Nom-iq Ltd. dba COM LAUDE
Registrar IANA ID: 470
Registrar Abuse Contact Email: abuse@comlaude.com
Registrar Abuse Contact Phone: +442074218250
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
Name Server: DNS1.COMLAUDE-DNS.COM
Name Server: DNS2.COMLAUDE-DNS.NET
Name Server: DNS3.COMLAUDE-DNS.CO.UK
Name Server: DNS4.COMLAUDE-DNS.EU
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2022-05-13T19:35:42Z
DNS Records
| Host | A Record | TTL |
|---|---|---|
| f1.com | 67.199.248.12 | 300 |
| f1.com | 67.199.248.13 | 300 |
| Host | MX Record | Priority | TTL |
|---|---|---|---|
| f1.com | f1-com.mail.protection.outlook.com | 10 | 300 |
| Host | NS Record | TTL |
|---|---|---|
| f1.com | dns1.comlaude-dns.com | 300 |
| f1.com | dns2.comlaude-dns.net | 300 |
| f1.com | dns3.comlaude-dns.co.uk | 300 |
| f1.com | dns4.comlaude-dns.eu | 300 |
| Host | TXT Record | TTL |
|---|---|---|
| f1.com | MS=ms13317307 | 300 |
| f1.com | yh4xmg69f2pkgqc7dmgks5gjkzbvdg93 | 300 |
| f1.com | 0ed1fe018a80cb3fd8405f4b7b8fdd4edfb104ce4a | 300 |
| f1.com | apple-domain-verification=f3BBbTYnmsg8mdZ0 | 300 |
| f1.com | docusign=142908a6-b577-4363-85b1-7a1374efe99d | 300 |
| f1.com | facebook-domain-verification=ftrjzgr3iiw25bw1aq50ryu0nat12t | 300 |
| f1.com | F6bSeogDsKvu600xTvzKSeB3gB4sJ4L2Mray4hEzHa7kcmjBY/LFJNZZ4LCklDibh9EW1fBHPnT4UkBp13pjmw== | 300 |
| f1.com | ciscocidomainverification=639065224ba42246237adf6c1634301c2c5bbed4aa606e685a9a725da8090702 | 300 |
| f1.com | atlassian-domain-verification=vApWx7DlLiqFlObDsEPzjtaAX/AIyBHSbJQi4Mte1v5XI5cNbumP1MCyseA+lmhc | 300 |
| f1.com | asv=a0a4bf541f171965c86de0c35c10b39c | 300 |
| f1.com | v=spf1 ip4:80.231.105.16 include:eu._netblocks.mimecast.com include:spf.protection.outlook.com include:spf.emailsignatures365.com include:spf.london.aquilaiajax.com ~all | 300 |
| f1.com | stripe-verification=558d0c1464f98248c5bc40f311e16e3119ebf71f40d426e5fed427acb0a8ddbf | 300 |
| f1.com | stripe-verification=bd6f964c54e62df78d79def27c68a2b4af1c0fd24c5cfbd19097c8cb0e3819b4 | 300 |
| f1.com | figma-domain-verification=3a999c62a1ccac311044d2e14b64c212acf8140e9ce80c6118f8a1c63c2e7f00-1723634965 | 300 |
dns1.comlaude-dns.com
TTL: 300
Email address: dnstech.comlaude.com
Serial: 2023051072
Refresh: 86400
Retry: 7200
Expire: 2419200
Minimum: 3600
Warnings
Consider avoiding viewport values that prevent users from resizing documents.
The “navigation” role is unnecessary for element “nav”.
The “main” role is unnecessary for element “main”.
Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
Empty heading.
Errors
Element “meta” is missing one or more of the following attributes: “content”, “property”.
Attribute “target” not allowed on element “button” at this point.
Bad value “100%” for attribute “height” on element “iframe”: Expected a digit but saw “%” instead.
Bad value “100%” for attribute “width” on element “iframe”: Expected a digit but saw “%” instead.
The “frameborder” attribute on the “iframe” element is obsolete. Use CSS instead.
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Bad value “Mar 23 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Mar 25 2018 16:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Mar 23 2018 13:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Mar 23 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Mar 23 2018 17:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Mar 24 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Mar 24 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Mar 24 2018 17:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Mar 24 2018 18:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
The text content of element “time” was not in the required format: The literal did not satisfy the time-datetime format.
Bad value “Apr 06 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 08 2018 18:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 06 2018 15:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 06 2018 18:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 06 2018 19:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 07 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 07 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 07 2018 18:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 07 2018 19:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 13 2018 10:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 15 2018 14:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 13 2018 11:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 13 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 13 2018 15:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 14 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 14 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 14 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 14 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 27 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 29 2018 16:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 27 2018 14:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 27 2018 17:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 27 2018 18:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 28 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 28 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 28 2018 17:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Apr 28 2018 18:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 11 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 13 2018 15:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 11 2018 12:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 11 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 11 2018 16:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 12 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 12 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 12 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 12 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 24 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 27 2018 15:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 24 2018 12:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 24 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 24 2018 16:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 26 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 26 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 26 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “May 26 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 08 2018 10:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 10 2018 14:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 08 2018 11:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 08 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 08 2018 15:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 09 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 09 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 09 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 09 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 22 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 24 2018 16:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 22 2018 13:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 22 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 22 2018 17:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 23 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 23 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 23 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 23 2018 17:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 29 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 01 2018 15:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 29 2018 12:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 29 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 29 2018 16:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 30 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 30 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 30 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jun 30 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 06 2018 10:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 08 2018 14:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 06 2018 11:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 06 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 06 2018 15:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 07 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 07 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 07 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 07 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 20 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 22 2018 15:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 20 2018 12:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 20 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 20 2018 16:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 21 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 21 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 21 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 21 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 27 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 29 2018 15:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 27 2018 12:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 27 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 27 2018 16:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 28 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 28 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 28 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Jul 28 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 24 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 26 2018 15:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 24 2018 12:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 24 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 24 2018 16:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 25 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 25 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 25 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 25 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 31 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 02 2018 15:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 31 2018 12:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 31 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Aug 31 2018 16:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 01 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 01 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 01 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 01 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 14 2018 16:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 16 2018 20:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 14 2018 18:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 14 2018 20:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 14 2018 22:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 15 2018 18:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 15 2018 19:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 15 2018 21:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 15 2018 22:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 28 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 30 2018 14:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 28 2018 12:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 28 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 28 2018 16:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 29 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 29 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 29 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Sep 29 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 05 2018 10:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 07 2018 14:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 05 2018 11:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 05 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 05 2018 15:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 06 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 06 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 06 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 06 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 19 2018 10:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 21 2018 13:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 19 2018 11:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 19 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 19 2018 15:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 20 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 20 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 20 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 20 2018 17:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 26 2018 10:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 28 2018 13:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 26 2018 11:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 26 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 26 2018 15:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 27 2018 10:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 27 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 27 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Oct 27 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 09 2018 11:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 11 2018 15:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 09 2018 12:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 09 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 09 2018 16:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 10 2018 12:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 10 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 10 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 10 2018 16:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 23 2018 13:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 25 2018 17:10” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 23 2018 14:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 23 2018 17:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 23 2018 18:30” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 24 2018 14:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 24 2018 15:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 24 2018 17:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “Nov 24 2018 18:00” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.
Bad value “extra-links” for attribute “role” on element “nav”.
End tag “div” seen, but there were open elements.
Unclosed element “footer”.
Stray end tag “footer”.
Stray end tag “div”.
Element “style” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)
Last tested: 05/12/2017
Desktop
Desktop Speed
54%
Optimize images
Leverage browser caching
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Avoid landing page redirects
Prioritize visible content
Enable compression
Minify HTML
Desktop Resource Breakdown
| Total Resources | 116 |
| Number of Hosts | 11 |
| Static Resources | 98 |
| JavaScript Resources | 18 |
| CSS Resources | 3 |
Last tested: 04/28/2017
Mobile
Mobile Usability
100%
Mobile Speed
36%
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Avoid landing page redirects
Optimize images
Enable compression
Minify HTML
Mobile Resource Breakdown
| Total Resources | 116 |
| Number of Hosts | 12 |
| Static Resources | 96 |
| JavaScript Resources | 21 |
| CSS Resources | 3 |
thaibinh.gov.vn
fontpuddle.com
hellocupcakebook.com
sothebysinstitute.com
transloc.com
cincinnatistate.edu
computerzone.pk
asiarussia.ru
boardgamequest.com
c******************s.com
f1.com
xedaptap.net
inforwebmultimedia.com
amjcaserep.com
futuristspeaker.com
ndn.info
quantum-journal.org
hmcourts-service.gov.uk
onlinesentinel.com
curious.com
databank.com
okna-komfort.com.ua
fontpuddle.com
hellocupcakebook.com
sothebysinstitute.com
transloc.com
cincinnatistate.edu
computerzone.pk
asiarussia.ru
boardgamequest.com
c******************s.com
f1.com
xedaptap.net
inforwebmultimedia.com
amjcaserep.com
futuristspeaker.com
ndn.info
quantum-journal.org
hmcourts-service.gov.uk
onlinesentinel.com
curious.com
databank.com
okna-komfort.com.ua
www.f1.com
www.f1.net
www.f1.org
www.f1.info
www.f1.biz
www.f1.us
www.f1.mobi
www.1.com
www.f1.com
www.c1.com
www.fc1.com
www.cf1.com
www.d1.com
www.fd1.com
www.df1.com
www.r1.com
www.fr1.com
www.rf1.com
www.t1.com
www.ft1.com
www.tf1.com
www.g1.com
www.fg1.com
www.gf1.com
www.v1.com
www.fv1.com
www.vf1.com
www.f.com
www.f1.con
www.f1.net
www.f1.org
www.f1.info
www.f1.biz
www.f1.us
www.f1.mobi
www.1.com
www.f1.com
www.c1.com
www.fc1.com
www.cf1.com
www.d1.com
www.fd1.com
www.df1.com
www.r1.com
www.fr1.com
www.rf1.com
www.t1.com
www.ft1.com
www.tf1.com
www.g1.com
www.fg1.com
www.gf1.com
www.v1.com
www.fv1.com
www.vf1.com
www.f.com
www.f1.con