Is Hornetsecurity Security Awareness Service down?
Current Hornetsecurity Security Awareness Service status is UP

Hornetsecurity is implementing an update to enhance email security by enforcing checks on the "Header-From" value in emails, as per RFC 5322 standards.
This initiative is driven by several key reasons:

1. Preventing Email Delivery Issues: Historically, not enforcing the validity of the originator email address has led to emails being accepted by our system but ultimately rejected by the final destination, especially with most customers now using cloud email service providers that enforce stricter validation.
2. Enhanced Protection Against Spoofed Emails: By strictly validating the "Header-From" value, we aim to significantly reduce the risk of email spoofing.
3. Enhance Email Authentication for DKIM/DMARC Alignment: By enforcing RFC 5322 compliance in the "Header-From" field, we can ensure better alignment with DKIM and DMARC standards, thereby significantly improving the security and authenticity of email communications.

The cause of malformed "From" headers often stems from incorrect email server configurations by the sender or from bugs in scripts or other applications. Our new protocol aims to rectify these issues, ensuring that all emails passing through our system are fully compliant with established standards, thus improving the overall security and reliability of email communications.

Implementation Timeline
· Stage 1 (Starting 4 March 2024): 1-5% of invalid emails will be rejected.
· Stage 2 (Second week): 30% rejection rate.
· Stage 3 (Third week): 60% rejection rate.
· Final Stage (By the end of the fourth week): 100% rejection rate.

You can find more information at our Knowledge Base:

English: https://support.hornetsecurity.com/hc/en-us/articles/22036971529617
German: https://support.hornetsecurity.com/hc/de/articles/22036971529617
Spanish: https://support.hornetsecurity.com/hc/es/articles/22036971529617
French: https://support.hornetsecurity.com/hc/fr/articles/22036971529617

Hornetsecurity is implementing an update to enhance email security by enforcing checks on the "Header-From" value in emails, as per RFC 5322 standards.
This initiative is driven by several key reasons:

1. Preventing Email Delivery Issues: Historically, not enforcing the validity of the originator email address has led to emails being accepted by our system but ultimately rejected by the final destination, especially with most customers now using cloud email service providers that enforce stricter validation.
2. Enhanced Protection Against Spoofed Emails: By strictly validating the "Header-From" value, we aim to significantly reduce the risk of email spoofing.
3. Enhance Email Authentication for DKIM/DMARC Alignment: By enforcing RFC 5322 compliance in the "Header-From" field, we can ensure better alignment with DKIM and DMARC standards, thereby significantly improving the security and authenticity of email communications.

The cause of malformed "From" headers often stems from incorrect email server configurations by the sender or from bugs in scripts or other applications. Our new protocol aims to rectify these issues, ensuring that all emails passing through our system are fully compliant with established standards, thus improving the overall security and reliability of email communications.

Implementation Timeline
· Stage 1 (Starting 4 March 2024): 1-5% of invalid emails will be rejected.
· Stage 2 (Second week): 30% rejection rate.
· Stage 3 (Third week): 60% rejection rate.
· Final Stage (By the end of the fourth week): 100% rejection rate.

You can find more information at our Knowledge Base:

English: https://support.hornetsecurity.com/hc/en-us/articles/22036971529617
German: https://support.hornetsecurity.com/hc/de/articles/22036971529617
Spanish: https://support.hornetsecurity.com/hc/es/articles/22036971529617
French: https://support.hornetsecurity.com/hc/fr/articles/22036971529617

Hornetsecurity is implementing an update to enhance email security by enforcing checks on the "Header-From" value in emails, as per RFC 5322 standards.
This initiative is driven by several key reasons:

1. Preventing Email Delivery Issues: Historically, not enforcing the validity of the originator email address has led to emails being accepted by our system but ultimately rejected by the final destination, especially with most customers now using cloud email service providers that enforce stricter validation.
2. Enhanced Protection Against Spoofed Emails: By strictly validating the "Header-From" value, we aim to significantly reduce the risk of email spoofing.
3. Enhance Email Authentication for DKIM/DMARC Alignment: By enforcing RFC 5322 compliance in the "Header-From" field, we can ensure better alignment with DKIM and DMARC standards, thereby significantly improving the security and authenticity of email communications.

The cause of malformed "From" headers often stems from incorrect email server configurations by the sender or from bugs in scripts or other applications. Our new protocol aims to rectify these issues, ensuring that all emails passing through our system are fully compliant with established standards, thus improving the overall security and reliability of email communications.

Implementation Timeline
· Stage 1 (Starting 4 March 2024): 1-5% of invalid emails will be rejected.
· Stage 2 (Second week): 30% rejection rate.
· Stage 3 (Third week): 60% rejection rate.
· Final Stage (By the end of the fourth week): 100% rejection rate.

You can find more information at our Knowledge Base:

English: https://support.hornetsecurity.com/hc/en-us/articles/22036971529617
German: https://support.hornetsecurity.com/hc/de/articles/22036971529617
Spanish: https://support.hornetsecurity.com/hc/es/articles/22036971529617
French: https://support.hornetsecurity.com/hc/fr/articles/22036971529617

Hornetsecurity is implementing an update to enhance email security by enforcing checks on the "Header-From" value in emails, as per RFC 5322 standards.
This initiative is driven by several key reasons:

1. Preventing Email Delivery Issues: Historically, not enforcing the validity of the originator email address has led to emails being accepted by our system but ultimately rejected by the final destination, especially with most customers now using cloud email service providers that enforce stricter validation.
2. Enhanced Protection Against Spoofed Emails: By strictly validating the "Header-From" value, we aim to significantly reduce the risk of email spoofing.
3. Enhance Email Authentication for DKIM/DMARC Alignment: By enforcing RFC 5322 compliance in the "Header-From" field, we can ensure better alignment with DKIM and DMARC standards, thereby significantly improving the security and authenticity of email communications.

The cause of malformed "From" headers often stems from incorrect email server configurations by the sender or from bugs in scripts or other applications. Our new protocol aims to rectify these issues, ensuring that all emails passing through our system are fully compliant with established standards, thus improving the overall security and reliability of email communications.

Implementation Timeline
· Stage 1 (Starting 4 March 2024): 1-5% of invalid emails will be rejected.
· Stage 2 (Second week): 30% rejection rate.
· Stage 3 (Third week): 60% rejection rate.
· Final Stage (By the end of the fourth week): 100% rejection rate.

You can find more information at our Knowledge Base:

English: https://support.hornetsecurity.com/hc/en-us/articles/22036971529617
German: https://support.hornetsecurity.com/hc/de/articles/22036971529617
Spanish: https://support.hornetsecurity.com/hc/es/articles/22036971529617
French: https://support.hornetsecurity.com/hc/fr/articles/22036971529617

We are investigating reports of Teachable Moment not loading as expected.

Other services are not affected.