Topic: Mx Records

4 chapters across the catalog

Sauerkraut Kid
Episode 1826 3:01 - 8:13

1826: Sauerkraut Kid

Google Safety Scam, Sophisticated Phishing Tactics

A host describes a sophisticated social engineering attempt involving a caller spoofing Google Safety and Security. The scammer utilized sites.google.com to host a fake ticket-closing portal and attempted to verify legitimacy by citing the host's MX records and sending spoofed emails from no-reply@google.com. The interaction ended when the host challenged the scammer to send an email from a corporate @google.com address.

Peak Whiteness
Episode 1248 1:44 - 7:17

1248: Peak Whiteness

Email Bombing Attack and Subscription Bot Tactics

One of the hosts experienced a massive email bombing attack starting at 5:30 AM on show day, receiving over 20,000 emails within hours. The attack utilized a sophisticated script or bot that automatically signed the host's email address up for thousands of newsletters and e-commerce sites globally, including many Russian services. Technical mitigation involved changing MX records and implementing Bayesian filters to manage the influx of unverified subscriptions.

Grapes the Size of Little Oranges
Episode 25 1:17:09 - 1:20:48

25: Grapes the Size of Little Oranges

Gmail Search Capabilities and MX Record Control

John C. Dvorak expresses his reluctance to depend on third-party email providers like Gmail, preferring to maintain control over his own mail servers. Adam Curry argues for the superior search capabilities of Gmail and explains how controlling the MX record in DNS settings provides the ultimate security against being locked out by a provider.

Never Say No to a Soldier
Episode 20 1:00:31 - 1:03:31

20: Never Say No to a Soldier

Private Email Hosting and Spam Prevention

Maintaining private email servers is presented as a more secure alternative to relying on major providers like Gmail or Yahoo. Using a private host allows for better control over spam filters and prevents data loss if a major service provider decides to terminate an account. Technical details regarding MX records and secondary servers are discussed as methods for ensuring reliable communication.