Home → The Fix! Newsletters → 2026 → Techno Mumbo Jumbo (What does it all mean Basil?)
1.4. Techno Mumbo Jumbo (What does it all mean Basil?)
Ok. So now we need to talk about some not so fun aka boring things that are still really important. They are IFRAME guest-facing site security, web site performance, and email deliverability. Arctic has released a few new features to help with all three. 🥱 😴 . . . No seriously, drink some caffeine and listen up. This stuff is important.
Access Control List For IFRAME
First let's talk about the new security control. If you are using the IFRAME implementation of the guest-facing site, there is a new setting to enable that will allow you to specify where the IFRAME should be. This is especially helpful if you have multiple domains where you have deployed your guest-facing site but should still be enabled even if you just have the IFRAME on your main domain.
The access control list tells the system which domains are approved to house your IFRAME(s). Any site not in the list will not be able to display the guest-facing site.
To learn more about the new ACL setting, see our documentation or reach out to support and we will be happy to help.
Preserving Web-site Performance
Another piece that Arctic recently deployed for ourselves and recommend that you craft for your own websites is an updated robots.txt file. We have recently seen a spike in traffic related to AI Agents/Crawlers specifically Learning Model AI that are sucking up a lot of server resources and impacting site performance. If unchecked the AI Agents/Crawlers can cause your site to load slowly which could negatively affect your guests' experience on your site.
If you haven't updated your robots.txt file in a while or you aren't even sure you have one, it would be good to reach out to your web person to check on your site performance and your current file to see if any improvements are needed.
We have laid out a brief explanation of the robots.txt file and provide a link to a GitHub resource to help you and your web person craft a robots.txt file that is right for your specific goals in our support documentation. In it, we also list what we chose to implement as a point of reference. If you or your web person have any questions about the robots.txt file we implemented, please contact us and we will be happy to help.
Advanced Email Configuration
As many of you are aware back in January of 2024, Gmail and Yahoo! implemented new sender regulations required to ensure smooth delivery of your emails. These requirements have since been picked up by most email providers. When these requirements came out, you could implement a DMARC "p" policy of "none" and the receiving systems would then check your SPF records and DKIM records to ensure that the sending domain sending the email on your behalf was an approved sender. This provided an additional check they could use when DMARC checks failed. What is DMARC you may ask? DMARC basically checks to see if the sending domain matches the domain in the "From" field. When you use Arctic's default mail features, DMARC checks do not pass because the mail coming from our servers comes from arcticres.com and therefore does not match the domain of the email addresses you use for your installation.
Most providers still deliver emails without any issues or challenges when the DMARC "p" policy is set to "none" and the proper DKIM and SPF records have been implemented. However, some mail providers have become more stringent and now want DMARC checks to pass in order to class your emails not as SPAM or in some cases deliver them at all.
To help with this challenge and resolve failed DMARC checks when using Arctic's default mail features, we have added an additional option to allow you to set up a subdomain on your main domain for your Arctic installation to use when sending emails on your behalf. This option requires your web person to create several records for you on your domain and is a multi-step process that goes back and forth between your web person and your Arctic installation to get fully completed. Since this is a more technologically complex process, if you would like to use it, you must reach out to support to get our assistance and we will be happy to guide you through the needed steps.
If you or your web person have any questions about the new advanced configuration option or would like to implement it for your installation, please contact us for further information.
Ok. So that's the end of those very important announcements. Thank you for paying attention. We can now resume our normally lighthearted banter and cheeky wit. Phew! I didn't think we would make it. 🤓