Skip to content

ELICA S.P.A. Trust Center

Security and compliance at ELICA S.P.A.

Monitor this supplier

Page updated

About

  • Industry Appliances

Security checks by ResilientX

Observed

5/8 public checks passed 5 of 8 public checks passed

Read from elica.com the way any browser or mail server would.

DNS

0 of 2 passed

  • DNSSEC

    Fail

    DNS answers for elica.com are not signed (no DNSSEC).

  • CAA record

    Attention

    No CAA record, so any certificate authority may issue certificates for elica.com.

Disclosure

0 of 1 passed

  • security.txt

    Fail

    No security.txt file, so researchers have no published way to report a vulnerability.

  • Trust page

    Info

    No trust or security page found at the usual addresses.

Email

2 of 2 passed

  • SPF

    Pass

    An SPF record lists the servers allowed to send mail for elica.com, and turns the rest away (-all).

  • DMARC

    Pass

    Mail pretending to come from elica.com is rejected (DMARC policy reject).

  • Mail servers

    Info

    One mail server receives mail for elica.com.

Website

3 of 3 passed

  • HTTPS

    Pass

    The website answers over HTTPS and sends plain HTTP visitors there.

  • TLS version

    Pass

    Connections use a current protocol (TLSv1.3).

  • Certificate

    Pass

    The certificate is valid until January 9, 2027.

These checks read what any browser or mail server can see. They are not a penetration test or an audit. Checked October 21, 2026.

Frequently asked questions

How secure is ELICA S.P.A.?

ResilientX measures ELICA S.P.A.’s cyber posture score from outside at 60.46 out of 100 (high exposure; lower is better) as of September 27, 2024. It is not an audit. Details

Is ELICA S.P.A. ISO 27001 certified?

ELICA S.P.A. has not published its certifications on its Trust Center yet.

Does ELICA S.P.A. use DMARC?

Yes. ELICA S.P.A. publishes a DMARC policy of reject, so mail pretending to come from elica.com is turned away.

Does ELICA S.P.A.’s website use HTTPS?

Yes. elica.com answers over HTTPS and sends plain HTTP visitors there, but does not tell browsers to insist on HTTPS (no HSTS).