IP Address: 2600:1901:101:2::

The address is hosted on Google LLC (GOOGLE-CLOUD). While major cloud platforms carry large volumes of legitimate mail, concentrations of authentication failures on specific ranges often indicate either a compromised customer account or a pattern of abuse-tolerant customer behavior within that range.

Across the wider GOOGLE-CLOUD network, 57 distinct IPs have been associated with 133 authentication failures over 154 observed messages, spanning 5 countries. Most observed IPs on this network contribute to the failure count, suggesting the range as a whole warrants elevated scrutiny.

For IPv6 addresses, per-address blocking provides minimal protection. Cloud providers and large networks typically allocate a full /64 prefix (containing approximately 18 quintillion addresses) to each customer. An attacker assigned a /64 can rotate through effectively unlimited addresses within the same prefix at no cost. Blocking should target the /48 or /64 prefix rather than the individual address.

If your domain appears in the From header of mail from this address, start with a misconfiguration investigation before assuming spoofing. Google's infrastructure is used by many legitimate senders, and auth failures here most often reflect a broken SPF include chain, a DKIM signing gap on a shared sending path, or a forwarding rule that breaks alignment. Verify that your authorized senders on Google are correctly publishing SPF and signing with DKIM before concluding the activity is malicious.

Your DMARC policy posture matters more than any IP-level response here. A p=none policy provides visibility but no enforcement, meaning mail is reported but not blocked. Moving to p=quarantine and then p=reject closes the gap for attackers who manage partial alignment. Domains that remain at p=none long-term tend to be impersonated repeatedly, because the cost to the attacker of attempting is effectively zero.

Blocking this individual address has limited durability: an attacker can rotate to another address in the same /24 subnet at effectively zero cost. More durable responses include monitoring aggregate DMARC reports so new sources are visible as they emerge, tightening SPF to remove overly permissive include chains or +all mechanisms, and ensuring DKIM is signing every legitimate outbound stream so alignment failures are unambiguous. The formal abuse contact for Google LLC is listed in ARIN WHOIS records, and timely remediation is achievable through that channel.