{"id":26225,"date":"2022-02-22T15:30:05","date_gmt":"2022-02-22T15:30:05","guid":{"rendered":"https:\/\/www.retarus.com\/blog\/retarus-makes-live-search-more-transparent-for-admins-and-partners\/"},"modified":"2026-08-07T15:05:46","modified_gmt":"2026-08-07T15:05:46","slug":"retarus-makes-live-search-more-transparent-for-admins-and-partners","status":"publish","type":"post","link":"https:\/\/www.retarus.com\/blog\/en\/retarus-makes-live-search-more-transparent-for-admins-and-partners\/","title":{"rendered":"A glimpse into the engine room: Retarus makes Live Search more transparent for admins and partners"},"content":{"rendered":"\n
The comprehensive, powerful search options offered by Retarus Email Live Search make it possible for administrators to always track which email security filters and rules have been applied to each message. By way of the user-friendly, browser-based myEAS Portal<\/a>, the search provides detailed results in real time, allowing remarkably fast analysis and IT forensics. Should a message go missing, for instance, this also allows support staff at the company or the Retarus partner<\/a> to provide end users with detailed information about its current whereabouts without undue efforts.<\/p>\n\n\n\n The search options and depth of detail are continuously expanded and enhanced by our team of developers. In just one of our recent developments, users now have access to a whole raft of additional insights (tracking points) related to our CxO Fraud Detection<\/a> filtering feature. In this way, Email Live Search now transparently provides information about which algorithm has been applied to each message while the filter was operating. This provides helpdesk staff with valuable additional information for processing tickets and support requests.<\/p>\n\n\n\n A little background on this topic: In the course of the CxO Fraud Detection service, the messages are analyzed by means of numerous different mechanisms. Each of these provides a certain percentage of fraud probability, which is measured against the probability threshold that has been configured \u2013 in order to place the message in quarantine if necessary. While all these algorithms are designed to detect bogus email senders, they each target a different spoofing<\/a> technique. Ultimately, knowing which vector of attack was employed also helps admins and partners to identify errors in their own configurations and fine-tune the corresponding threshold.<\/p>\n\n\n\nNew tracking points allow behind-the-scenes insight<\/h2>\n\n\n\n
Detailed analysis: Which vector of attack was employed? <\/h2>\n\n\n\n