genialinvestimentos.com.br security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

19risk

Low

Minor observations only.

0Critical

0High

1Medium

4Low

1Info

Collected 8 hours ago3.8sfrom cache

Headers—

unavailable

Certificate Transparency69
DNS resolution19
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs60
Registration
DNS posture2
Email authentication2
Certificate
Security headers
Archived URLs
Analysis6

noteFound 69 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 13 addresses; enriching the first 12.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
noteSecurity headers did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.
note4 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: genialinvestimentos.com.br
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 13.110.204.15:25
plataforma-api-dev.genialinvestimentos.com.br appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: plataforma-api-dev.genialinvestimentos.com.br
www.old.genialinvestimentos.com.br appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.old.genialinvestimentos.com.br
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: genialinvestimentos.com.br
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: genialinvestimentos.com.br

✓Receives mail via 2 servers
mxa-00944301.gslb.pphosted.com mxb-00944301.gslb.pphosted.com
✓SPFends in -all
v=spf1 include:spf-00944301.pphosted.com include:cust-spf.exacttarget.com include:spf.protection.outlook.com include:servers.mcsv.net include:spf.mandrillapp.com include:spfhost.messageprovider.com include:mail.zendesk.com ip4:189.125.206.209/32 ip4:179.191.91.0/26 ip4:200.142.102.0/26 ip4:177.154.156.146/30 ip4:177.154.156.150/30 ip4:45.177.100.82/28 ip4:179.190.21.208/29 ip4:186.224.192.224/28 ip4:201.48.79.248/29 include:spf-us.emailsignatures365.com include:_spf.salesforce.com -all
✓DMARCp=reject
v=DMARC1; p=reject; fo=1; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 issue "amazon.com" · 0 issue "amazonaws.com" · 0 issue "amazontrust.com" · 0 issue "awstrust.com" · 0 issue "comodoca.com" · 0 issue "digicert.com; cansignhttpexchanges=yes" · 0 issue "letsencrypt.org" · 0 issue "pki.goog; cansignhttpexchanges=yes" · 0 issue "ssl.com" · 0 issuewild "amazon.com" · 0 issuewild "amazonaws.com" · 0 issuewild "amazontrust.com" · 0 issuewild "awstrust.com" · 0 issuewild "comodoca.com" · 0 issuewild "digicert.com; cansignhttpexchanges=yes" · 0 issuewild "letsencrypt.org" · 0 issuewild "pki.goog; cansignhttpexchanges=yes" · 0 issuewild "ssl.com"
–IPv6 (AAAA)IPv4 only
✓2 nameservers
jade.ns.cloudflare.com nick.ns.cloudflare.com

✓Registered9.4 years old
genialinvestimentos.com.br
✓Registration expiry210 days
2027-04-05
✗Transfer lock
none
✓2 nameservers at registry
jade.ns.cloudflare.com nick.ns.cloudflare.com

Address	Ports	Edge	Network
172.64.153.235 lp.genialinvestimentos.com.br +3	80443205220532082208320862087+5	Cloudflare~	—
104.18.34.21 lp.genialinvestimentos.com.br +3	80443205220532082208320862087+5	Cloudflare~	—
172.66.153.191 hb.genialinvestimentos.com.br +4	80443205220532082208320862087+5	Cloudflare~	—
104.20.40.32 hb.genialinvestimentos.com.br +4	80443205220532082208320862087+5	Cloudflare~	—
96.17.96.18 genialinvestimentos.com.br +95	80443	direct	—
96.17.96.29 genialinvestimentos.com.br +2	80	direct	—
201.20.16.40 cs.genialinvestimentos.com.br +1	179	direct	—
191.232.163.41 sbc.genialinvestimentos.com.br	5070	direct	—
13.110.204.15 email.genialinvestimentos.com.br +6	25	direct	—
23.215.7.32 blog.genialinvestimentos.com.br +1	80	direct	—
23.215.7.28 blog.genialinvestimentos.com.br +1	80	direct	—
179.191.91.8 sso.genialinvestimentos.com.br	none known	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

genialinvestimentos.com.br security report

Low

Findings

Email authentication

DNS

Registration

Hosts

Hostnames