# Suspicious login emails coming from all over

**URL:** <https://meta.discourse.org/t/suspicious-login-emails-coming-from-all-over/113706>\
**Category:** Feature\
**Created:** [April 8, 2019, 12:52am UTC](https://meta.discourse.org/t/suspicious-login-emails-coming-from-all-over/113706 "2019-04-08T00:52:59Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)\
**Post date:** [April 8, 2019, 4:36am UTC](https://meta.discourse.org/t/suspicious-login-emails-coming-from-all-over/113706/7 "2019-04-08T04:36:49Z")

</div>

Yep, there are no real geographical constraints for subnets. They’re allocated to providers and in a lot of cases the networks will only update their records once or twice a year.

On top of that mess, all of the IP lookup databases who compile that data are effectively best-effort.

There was a time that certain providers gave each customer a static address with lookup data that was _too_ accurate. Of the two approaches I guess the former is preferable?

---

_[View the full topic](https://meta.discourse.org/t/suspicious-login-emails-coming-from-all-over/113706)._
