lance.com.br was registered with whois.registro.br on 12 Jun 1996 and is hosted on AS13335 CloudFlare Inc. in United States of America. Its SSL certificate from "Cloudflare expired on 29 Oct 2024, and the site does not support HTTP/3. WOT's community rates its safety good (63/100).
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Is lance.com.br’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Brazil | 96.8% | 29,970,604 | 6.7% | 93.3% |
| United Kingdom | 2% | 632,482 | 0.2% | 99.9% |
| Portugal | 0.5% | 144,208 | 9.5% | 90.5% |
| United States | 0.3% | 83,346 | 33.9% | 66.1% |
| Argentina | 0.2% | 68,450 | 4.2% | 95.8% |
1 technology detected across 1 category.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address lance.com.br resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| lance.com.br | 104.18.14.60 | 300 |
| lance.com.br | 104.18.15.60 | 300 |
| Host | IPv6 address | TTL |
|---|---|---|
| lance.com.br | 2606:4700::6812:e3c | 300 |
| lance.com.br | 2606:4700::6812:f3c | 300 |
| Host | Mail server | TTL |
|---|---|---|
| lance.com.br | 10 aspmx.l.google.com | 300 |
| lance.com.br | 10 mx01.cluster01.messagingcentral.net | 300 |
| lance.com.br | 20 alt1.aspmx.l.google.com | 300 |
| lance.com.br | 20 alt2.aspmx.l.google.com | 300 |
| lance.com.br | 20 mx02.cluster01.messagingcentral.net | 300 |
| lance.com.br | 30 aspmx2.googlemail.com | 300 |
| lance.com.br | 30 aspmx3.googlemail.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| lance.com.br | donovan.ns.cloudflare.com | 21600 |
| lance.com.br | laura.ns.cloudflare.com | 21600 |
| Host | Text | TTL |
|---|---|---|
| lance.com.br | "\"google-site-verification=SYnGeq-tFHdo-IjnIGjJdIqKRCVx-m0sj6cdmwg8MkM\"\"google-site-verification=GTwsiifNO4GDKtGgqYlbI_I6fqW2bAwdafU6MXyX-gQ\"\"ca3-d62b8065b9c24c369a566b07cf67ee45\"\"ca3-c3afeb0268b0481a837f9082bb5ccc5c\"\"google-site-verification=XIPEZ2ZRyMTkS" "p179kQGDxStF5REMvbHp2Tnf8soZ34\"\"v=spf1 mx ip4:200.150.150.128/27 ip4:200.150.150.0/26 include:_spf.rdstation.com.br include:_spf.google.com -all\"" | 300 |
| lance.com.br | "v=spf1 mx ip4:200.150.150.128/27 ip4:200.150.150.0/26 include:_spf.rdstation.com.br include:_spf.google.com -all" | 300 |
| Host | Policy | TTL |
|---|---|---|
| lance.com.br | 0 issue comodoca.com | 3600 |
| lance.com.br | 0 issue digicert.com\; cansignhttpexchanges=yes | 3600 |
| lance.com.br | 0 issue letsencrypt.org | 3600 |
| lance.com.br | 0 issue pki.goog\; cansignhttpexchanges=yes | 3600 |
| lance.com.br | 0 issuewild comodoca.com | 3600 |
| lance.com.br | 0 issuewild digicert.com\; cansignhttpexchanges=yes | 3600 |
| lance.com.br | 0 issuewild letsencrypt.org | 3600 |
| lance.com.br | 0 issuewild pki.goog\; cansignhttpexchanges=yes | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| lance.com.br | donovan.ns.cloudflare.com dns.cloudflare.com 2329482523 10000 2400 604800 1800 | 1800 |
| Host | Value | TTL |
|---|---|---|
| lance.com.br | 256 3 13 oJMRESz5E4gYzS/q6XDrvU1qMPYIjCWzJaOau8XNEZeqCYKD5ar0IRd8KqXXFJkqmVfRvMGPmM1x8fGAa2XhSA== | 3600 |
| lance.com.br | 257 3 13 mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ== | 3600 |
Other domains served from 104.18.15.60. Normal for shared hosting and CDNs.
No reviews yet. Used lance.com.br? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
WOT's community rates lance.com.br good for safety (63/100). Its SSL certificate expired on 29 Oct 2024. See Security →
lance.com.br is registered through whois.registro.br. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expired on 12 Jun 2024. See Overview →
lance.com.br was registered on 12 Jun 1996, making it 30 years old. See Overview →
lance.com.br is served from 2 IP addresses, mainly on AS13335 CloudFlare Inc. in United States of America. See Hosting →
We detected 1 technology, including Google Analytics. See Built with →
Raw registry data for lance.com.br. May be redacted by privacy services.
% Copyright (c) Nic.br % The use of the data below is only permitted as described in % full by the Use and Privacy Policy at https://registro.br/upp , % being prohibited its distribution, commercialization or % reproduction, in particular, to use it for advertising or % any similar purpose. % 2024-01-09T22:52:54-03:00 - IP: 38.137.4.82 domain: lance.com.br owner: LANCE WEB LTDA owner-c: LAWLT2 tech-c: TELWE nserver: laura.ns.cloudflare.com nsstat: 20240107 AA nslastaa: 20240107 nserver: donovan.ns.cloudflare.com nsstat: 20240107 AA nslastaa: 20240107 created: 19960613 #9566 changed: 20231116 expires: 20240613 status: published nic-hdl-br: LAWLT2 person: LANCE WEB LTDA created: 20210809 changed: 20211001 nic-hdl-br: TELWE person: Tecnologia Lance Web created: 20230406 changed: 20230406 % Security and mail abuse issues should also be addressed to % cert.br, http://www.cert.br/ , respectivelly to [email protected] % and [email protected] % % whois.registro.br accepts only direct match queries. Types % of queries are: domain (.br), registrant (tax ID), ticket, % provider, CIDR block, IP and ASN.
The first response from http://www.lance.com.br, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with lance.com.br. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.