idsecure.com.br was registered with whois.registro.br on 18 Nov 2020 and is hosted on AS16509 Amazon.com Inc. in United States of America. Its SSL certificate from Amazon expired on 29 Apr 2026, and the site does not support HTTP/3.
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 idsecure.com.br’s name taken on other extensions?
Estimated visitors and engagement.
1 technology detected across 1 category.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address idsecure.com.br resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| idsecure.com.br | 13.33.252.37 | 60 |
| idsecure.com.br | 13.33.252.38 | 60 |
| idsecure.com.br | 13.33.252.75 | 60 |
| idsecure.com.br | 13.33.252.88 | 60 |
| Host | Name server | TTL |
|---|---|---|
| idsecure.com.br | ns-1115.awsdns-11.org | 21600 |
| idsecure.com.br | ns-1639.awsdns-12.co.uk | 21600 |
| idsecure.com.br | ns-219.awsdns-27.com | 21600 |
| idsecure.com.br | ns-860.awsdns-43.net | 21600 |
| Host | Policy | TTL |
|---|---|---|
| idsecure.com.br | 0 issuewild amazon.com | 60 |
| idsecure.com.br | 0 issuewild amazonaws.com | 60 |
| idsecure.com.br | 0 issuewild amazontrust.com | 60 |
| idsecure.com.br | 0 issuewild awstrust.com | 60 |
| idsecure.com.br | 0 issuewild letsencrypt.org | 60 |
| Host | Start of authority | TTL |
|---|---|---|
| idsecure.com.br | ns-219.awsdns-27.com awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
Other domains served from 13.33.252.38. Normal for shared hosting and CDNs.
No reviews yet. Used idsecure.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.
idsecure.com.br has no community safety rating yet. Its SSL certificate expired on 29 Apr 2026. See Security →
idsecure.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 expires on 18 Nov 2030 — in 4 years. See Overview →
idsecure.com.br was registered on 18 Nov 2020, making it 5 years old. See Overview →
idsecure.com.br is served from 4 IP addresses, mainly on AS16509 Amazon.com Inc. in United States of America. See Hosting →
We detected 1 technology, including Google Analytics. See Built with →
Raw registry data for idsecure.com.br. May be redacted by privacy services.
% Copyright (c) Nic.br - Use of this data is governed by the Use and % Privacy Policy at https://registro.br/upp . Distribution, % commercialization, reproduction, and use for advertising or similar % purposes are expressly prohibited. % 2025-06-01T18:57:20-03:00 - 104.239.13.205 domain: idsecure.com.br owner: Controlid Comercio de Hardware e Servicos de tecno owner-c: MJE5 tech-c: MJE5 nserver: ns-1115.awsdns-11.org nsstat: 20250531 AA nslastaa: 20250531 nserver: ns-1639.awsdns-12.co.uk nsstat: 20250531 AA nslastaa: 20250531 nserver: ns-219.awsdns-27.com nsstat: 20250531 AA nslastaa: 20250531 nserver: ns-860.awsdns-43.net nsstat: 20250531 AA nslastaa: 20250531 saci: yes created: 20201119 #22047073 changed: 20220627 expires: 20301119 status: published nic-hdl-br: MJE5 person: Marcelo Jorge Epstein created: 20010430 changed: 20240227 % Security and mail abuse issues should also be addressed to cert.br, % respectivelly to [email protected] and [email protected] % % whois.registro.br only accepts exact match queries for domains, % registrants, contacts, tickets, providers, IPs, and ASNs.
The first response from http://www.idsecure.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 idsecure.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.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.