Account Creation Using Mail Server

I'm glad I stumbled upon this community, it seems like there are a lot of knowledgeable developers here, especially when it comes to Instagram account creation. I'm relatively new to this scene, having only been creating accounts for about 3 months now.

I am currently using following data while creating;

Proxy: ProxyCheap resedential sessions
Creation-Method: API calls via computer browser
Intial 2FA: Custom emails domains

I've been using ProxyCheap residential sessions and making API calls via my computer browser to create accounts. For the initial 2FA, I've been using custom email domains. I started out with number verifications using 5sim, but it was slow and the profit margin wasn't great, especially when trying to target bulk account buyers. So, I switched to email registration and set up my own custom mail server with about 25 domains. I've noticed that the domain extension doesn't seem to matter, and I'm using unique aliases for each account, never reusing emails. I'm also matching the name and email alias when creating accounts, and I'm using a fake person database to make the account names look legit.

Initially, I was able to create about 25 accounts within 4 minutes before hitting around 10 signup blocks. This wasn't a major issue, as I could just wait a bit and then repeat the process. However, over the past few days, I've been getting a massive amount of signup blocks. If I send out 30 final account creation requests, about 16 of them will result in a signup block. Instagram's error message suggests that this is due to my IP address being flagged as an open proxy, but I'm not entirely convinced.

The error message I'm getting is:
```
{
account_created: false,
errors: {
ip: [
'The IP address that you are using has been flagged as an open proxy. If you believe this to be incorrect, please visit https://help.instagram.com/'
]
},
status: 'ok',
error_type: 'signup_block'
}
```

I'm wondering if anyone has any experience with this issue, and if using higher quality proxies, such as LTE 4G proxies, could help bypass it. Alternatively, I'm concerned that Instagram might be limiting my domains because they all point to the same VPS hostname. Any advice or insights would be greatly appreciated.

**Note:** I am using all best practices such as making sure all network requests parameters are unique for each unique account attempted to be created. I have a bunch of fingerprints and ua's . I also ensure to use all the static tokens where instagram expects them. This does not seem to be a issue of identifiable by network-requests.
In my mind it's either the domains DNS being tracked and limited. Or the proxy's I have been using are
exhausted. I would really appricaite any insight or additional ideas.

An important part, is to make sure your alter thing fingerprints. You can also hide them, however altering them is very good.

havent thought about creating my own mailserver for creating account before , cool idea , could ease up some things. i dont understand why dont you believe the message though..

ToyBox | IG Accounts said:

An important part, is to make sure your alter thing fingerprints. You can also hide them, however altering them is very good.

Click to expand...

Thank you for you're response, I do in fact alter the fingerprint completely for each new account being created. It it in fact true a mobile proxy is preferred over residential?

soulmaster01 said:

havent thought about creating my own mailserver for creating account before , cool idea , could ease up some things. i dont understand why dont you believe the message though..

Click to expand...

I say this because the I.P's I am using are resedential and session based, I checked against a blacklist and they seem clean. I have experience with IG giving you misleading errors purposefully in the past. So yeah I am getting 'signup_block'. But I am doubtfull it's only based on I.P . Hope that makes sense.

yeah maybe try selenium script to automate the proccess more naturally. could lower the rate of generation compared to direct api calls but should have better results.

Because you registered via API, I will assume that you have faked the device info every time you call the API, so I will not mention it like everyone else. I will focus on the issue you are thinking about, which is proxy.

1. Instagram has been spammed for decades, so the residential proxy ranges seem to have been reused too many times. I haven't used your proxy provider, but I guess the ranges are usually similar, with a pool of around 100 million proxies being a lot for other social networks, but very small for Instagram. Therefore, normally to register on Instagram, people often set up a private mobile proxy pool to ensure the proxies are of good quality, and even when setting up a private pool, if exploitation occurs strongly, there will come a time when the mobile pool created will also be blacklisted, and they will have to change locations to use a different IP range.

2. Not only devices, but proxies also have fingerprints. At the simplest level, HTTPS proxies are always easier to detect than SOCKS5, and with Instagram, it is much more complicated. You need proxies that have been undetected at multiple layers along with knowledge of proxy fingerprints.

3. The Browser API is of much lower quality compared to the Mobile API.

Banoza said:

Because you registered via API, I will assume that you have faked the device info every time you call the API, so I will not mention it like everyone else. I will focus on the issue you are thinking about, which is proxy.

1. Instagram has been spammed for decades, so the residential proxy ranges seem to have been reused too many times. I haven't used your proxy provider, but I guess the ranges are usually similar, with a pool of around 100 million proxies being a lot for other social networks, but very small for Instagram. Therefore, normally to register on Instagram, people often set up a private mobile proxy pool to ensure the proxies are of good quality, and even when setting up a private pool, if exploitation occurs strongly, there will come a time when the mobile pool created will also be blacklisted, and they will have to change locations to use a different IP range.

2. Not only devices, but proxies also have fingerprints. At the simplest level, HTTPS proxies are always easier to detect than SOCKS5, and with Instagram, it is much more complicated. You need proxies that have been undetected at multiple layers along with knowledge of proxy fingerprints.

3. The Browser API is of much lower quality compared to the Mobile API.

Click to expand...

Amazing, this is the exact type of response I was looking for. I have also indeed noticed that when switching to my mentioned proxy provider registration worked fine for a few days. After some time the blocking started occurring, this would be inline with what you are mentioning.

When you mention > "people often set up a private mobile proxy pool to ensure the proxies are of good quality" is there a provider who offers such services. Or are you creating you're own batch of proxies from you're own VPS via subnets, I am only slightly familiar with creating own proxies. But it seems to gain about 1000 proxies you need ~6months to gain a good enough reputation on the I.P's to actually utilize them.

I appreciate you mentioning proxy's are also known to be fingerprinted, this is new knowledge to me. Al tough it does make allot of sense! Interesting that utilizing SOCKS5 protocol is harder to recognise a fingerprint, I will learn more about this and proxy fingerprinting in general.

On the note of browser API being worse than mobile API, I have had allot of success with browser API so far. I might look into also working with mobile but for now I have no reason to do so. As I only focus on account creation, not emulating actions on the accounts.

Final Quesiton:
Could you please point me to private mobile proxy pool provider, who's reputation would ensure that the I.P's are indeed fresh and high quality, preferred SOCKS5?

Thank you allot 0-0,
Implement.

I concur with the point about proxy -- residential proxies have much lower trust factor with the platforms. Go with a mobile proxy and test with one - no need to overdo it while you are testing and tweaking your setup. Just search here on BHW (or on Google) for mobile proxy providers, see which have a good reputation, and sign for a private (not shared) mobile proxy in the geo that you are targeting for the account creation. Rotate the IP for each account creation and see how it goes. If the result is good, then you can scale up and get multiple of those proxies (a "pool") to speed up your process.

AspiringNomad said:

I concur with the point about proxy -- residential proxies have much lower trust factor with the platforms. Go with a mobile proxy and test with one - no need to overdo it while you are testing and tweaking your setup. Just search here on BHW (or on Google) for mobile proxy providers, see which have a good reputation, and sign for a private (not shared) mobile proxy in the geo that you are targeting for the account creation. Rotate the IP for each account creation and see how it goes. If the result is good, then you can scale up and get multiple of those proxies (a "pool") to speed up your process.

Click to expand...

This does seem to be the common consensuses, I'll indeed try this approach. Is there any private mobile proxy provider you could recommend. As some of the prices I am seeing floating around seem outrageous. I appreciate you're reply!

I using vpn for account create

implement said:

This does seem to be the common consensuses, I'll indeed try this approach. Is there any private mobile proxy provider you could recommend. As some of the prices I am seeing floating around seem outrageous. I appreciate you're reply!

Click to expand...

They are indeed the priciest given that they are based off of sim cards. In terms of recommendation, BHW tends to flag when external services are recommended and, also, providers vary from region to region. But go to the Proxies For Sale section here on BHW and there are plenty listed. Also, do a search for mobile proxies, then do your own research on which are recommended for your geo.

Rakley said:

careful, that's not safe enough

Click to expand...

How its not safe? I can give a démo accounts to you and you can check them.

You’re on the right track, but ProxyCheap resi sessions get flagged often, especially at scale. That “open proxy” error usually means IG already fingerprinted your subnet. 4G/LTE proxies can help a lot with trust scores, especially if you rotate well. Also, if all your mail domains hit the same VPS IP, IG might be connecting the dots. Try spreading email hosting across different IPs/providers if possible. Solid setup overall—just needs cleaner proxy + domain separation.

Does mail server really work for account creation

implement said:

I'm glad I stumbled upon this community, it seems like there are a lot of knowledgeable developers here, especially when it comes to Instagram account creation. I'm relatively new to this scene, having only been creating accounts for about 3 months now.

I am currently using following data while creating;

Proxy: ProxyCheap resedential sessions
Creation-Method: API calls via computer browser
Intial 2FA: Custom emails domains

I've been using ProxyCheap residential sessions and making API calls via my computer browser to create accounts. For the initial 2FA, I've been using custom email domains. I started out with number verifications using 5sim, but it was slow and the profit margin wasn't great, especially when trying to target bulk account buyers. So, I switched to email registration and set up my own custom mail server with about 25 domains. I've noticed that the domain extension doesn't seem to matter, and I'm using unique aliases for each account, never reusing emails. I'm also matching the name and email alias when creating accounts, and I'm using a fake person database to make the account names look legit.

Initially, I was able to create about 25 accounts within 4 minutes before hitting around 10 signup blocks. This wasn't a major issue, as I could just wait a bit and then repeat the process. However, over the past few days, I've been getting a massive amount of signup blocks. If I send out 30 final account creation requests, about 16 of them will result in a signup block. Instagram's error message suggests that this is due to my IP address being flagged as an open proxy, but I'm not entirely convinced.

The error message I'm getting is:
```
{
account_created: false,
errors: {
ip: [
'The IP address that you are using has been flagged as an open proxy. If you believe this to be incorrect, please visit https://help.instagram.com/'
]
},
status: 'ok',
error_type: 'signup_block'
}
```

I'm wondering if anyone has any experience with this issue, and if using higher quality proxies, such as LTE 4G proxies, could help bypass it. Alternatively, I'm concerned that Instagram might be limiting my domains because they all point to the same VPS hostname. Any advice or insights would be greatly appreciated.

Click to expand...

Bro how do u catch the api calls and automate them??