# Last IP vs. Registration and Posting IP

**URL:** <https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884>\
**Category:** Feature\
**Created:** [April 19, 2014, 10:54am UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884 "2014-04-19T10:54:46Z")\
**Posts on this page:** 10\
**Page:** 1

## AI-generated summary

In a discussion titled "Last IP vs. Registration and Posting IP" under the Feature category, users debate the utility of tracking both Registration IP and Last IP for spam control and account moderation. [Mittineague](/t/-/14884/1) highlights how Registration IP has been instrumental in identifying abusive accounts—over 180K linked to banned users—and suggests that using both IPs improves moderation accuracy. [TechnoBear](/t/-/14884/5) clarifies that Discourse currently uses Last IP for moderation unless no posts exist, in which case Registration IP is used. [neil](/t/-/14884/6) confirms a recent update: when an admin deletes a user and blocks their email/IP, the Registration IP is also blocked if different from the Last IP, enhancing anti-spam measures. [codinghorror](/t/-/14884/3) supports having both IPs for better moderation, while [cpradio](/t/-/14884/9) adds that Registration IP helps detect multi-account abuse and setup posts. [Mittineague](/t/-/14884/7) expresses gratitude for the update, noting that other moderators will appreciate the improvement. The consensus is that combining both IPs provides a more robust system for identifying and preventing spam and abuse, especially when spammers register multiple accounts from the same IP before switching to proxies for posting.

<div class="post-metadata">

**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
**Post date:** [April 19, 2014, 10:54am UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884/1 "2014-04-19T10:54:47Z")

</div>

Continuing the discussion from [What about the spam problem?](https://meta.discourse.org/t/what-about-the-spam-problem/2724/10):

I have reservations about outright blocking by IP. But …

Even though the number of IPs that can be abused is effectively infinite. I have found it extremely helpful using Registration IP to identify possible and probable problem accounts. - I currently have over 180K associated with Banned accounts.

Most often the IP used to register is not the same IP used to post.

Unless I’m wrong, it seems that Discourse uses the Last IP. i.e.  
if no posts == registration IP  
else == posting IP

I strongly believe that having both would be of great benefit for moderating.

Any chance of getting this worked into the Core?

My thinking is we’ll be writing custom code to enhance moderation anyway, but we can only work with what information is available.

@zogstrip ??

---

<div class="post-metadata">

**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\
**Post date:** [April 23, 2014, 1:56pm UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884/2 "2014-04-23T13:56:59Z")

</div>

@neil what do you think?

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [April 24, 2014, 2:39am UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884/3 "2014-04-24T02:39:11Z")

</div>

I think having both is always a good idea, more info is better.

---

<div class="post-metadata">

**Author:** ![neil](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neil/32/102150_2.png) [@neil](https://meta.discourse.org/u/neil)\
**Post date:** [April 28, 2014, 8:20pm UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884/4 "2014-04-28T20:20:10Z")

</div>

(I swear I answered this, but apparently not.) Yes, I think it’s a good idea. I’ll add it.

---

<div class="post-metadata">

**Author:** ![TechnoBear](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/technobear/32/40546_2.png) [@TechnoBear](https://meta.discourse.org/u/TechnoBear)\
**Post date:** [April 29, 2014, 9:25am UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884/5 "2014-04-29T09:25:58Z")

</div>

[quote=“Mittineague, post:1, topic:14884”]  
Unless I’m wrong, it seems that Discourse uses the Last IP.  
i.e.if no posts == registration IP  
else == posting IP  
[/quote]Not necessarily post IP; it seems to record last log-in IP, whether a post was made or not.

---

<div class="post-metadata">

**Author:** ![neil](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neil/32/102150_2.png) [@neil](https://meta.discourse.org/u/neil)\
**Post date:** [April 29, 2014, 6:45pm UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884/6 "2014-04-29T18:45:38Z")

</div>

I added this today. It shows in admin below the last ip address:

![](https://global.discourse-cdn.com/meta/original/2X/f/fdc92c098298f6c26e1c315cf137f11769ca6fc3.png)

Also, when an admin deletes a user and chooses to block their email and ip address from signing up again, it will also block the registration ip address if it’s different than the last ip address.

---

<div class="post-metadata">

**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
**Post date:** [April 29, 2014, 7:42pm UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884/7 "2014-04-29T19:42:04Z")

</div>

Great! Thank you very very much.

I’m certain that some of the other Mods eg. @TechnoBear and @cpradio will be as pleased as I

I’m not a SPAMmer so I don’t know for sure, but it seems like often someone or something Registers a mess of accounts using the same IP, then sells the accounts to others that use a lot of different proxy IPs to make posts.

There are an awful lot of common IPs abused for making posts, true, but I have found that Reg IPs are more accurate for spotting and identifying problem accounts so this is indeed great news.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [April 29, 2014, 10:52pm UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884/8 "2014-04-29T22:52:33Z")

</div>

> [@neil](#):
>
> hen an admin deletes a user and chooses to block their email and ip address from signing up again, it will also block the registration ip address if it’s different than the last ip address.

![](https://global.discourse-cdn.com/meta/original/2X/0/0dc6d75831fa303d7a6de2a305172eea8c5c41d8.gif)

---

<div class="post-metadata">

**Author:** ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)\
**Post date:** [April 30, 2014, 1:48am UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884/9 "2014-04-30T01:48:38Z")

</div>

It also usually helps identify someone using multiple accounts, or setup posts. It just gives us another tool to take into account when investigating suspicious topics.

---

<div class="post-metadata">

**Author:** ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)\
**Post date:** [December 4, 2025, 11:10am UTC](https://meta.discourse.org/t/last-ip-vs-registration-and-posting-ip/14884/10 "2025-12-04T11:10:03Z")

</div>

Archived on December 4, 2025, 11:10am UTC


