#1 2023-04-10 2:30 pm

sb73542

Member

Registered: 2013-11-27

Posts: 5

Disposable email domains automatically flagged in SFS?

Hi there, I was trying to create a few test accounts on my forum, which uses SFS. It blocked the accounts that were registered @mitigado.com and @tutuapp.bid, which are disposable email domains. However, I can't find either of the randomly created addresses at those domains in the SFS search engine. Have they been automatically added as suspicious to the API query results or something? I also found at least one account recently registered to an @gmail.com address that wasn't in the SFS database. The SFS plugin for my forum supposedly only checks against the registered email, not IP or username, but I'm not sure if it's working correctly. Thanks for the help!

Alex Kemp

Moderator

From: Nottingham, England

Registered: 2009-12-02

Posts: 2,423

Website

Re: Disposable email domains automatically flagged in SFS?

I do not know the answer, so have sent a PM to pedigree (site admin).

---

Alex Kemp

IP Aggregation (Help) · Easy Firewall Generator (Help)  · Conteg v0.13.14

sb73542

Member

Registered: 2013-11-27

Posts: 5

Re: Disposable email domains automatically flagged in SFS?

Thanks Alex, appreciate it.

Oblivian

Member

Registered: 2018-11-04

Posts: 79

Re: Disposable email domains automatically flagged in SFS?

If you put @tutuapp.bid in search here, yes you can see it is a toxic address flag.

sb73542

Member

Registered: 2013-11-27

Posts: 5

Re: Disposable email domains automatically flagged in SFS?

Thanks for the reply, looks like I needed to add the @ to make it appear in the search results.

pedigree

uıɐbɐ ʎɐqǝ ɯoɹɟ pɹɐoqʎǝʞ ɐ buıʎnq ɹǝʌǝu ɯ,ı

From: New Zealand

Registered: 2008-04-16

Posts: 7,056

Re: Disposable email domains automatically flagged in SFS?

not automatically no but if a domain shows hostile intent such as highly randomised email accounts typically used to bypass exact email string matching, and it appears in google below stopforumspam when searching for that domain, then it goes in the blacklist.
you can turn off blacklist checking with &nobademail parameter