You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tricky part is to determine what is relevant (and this needs discussing) (and all after the pattern/regex-filter was applied)
Alexa ranking (??)
Anything that contains .mil, .gov
Anything that 'hackers' usually are interested in (e.g. "git.", "gw." "test.") and if there are multiple choices then exclude ".your-server.de" or DSL homelinks (e.g. give them least pagerank).
If the USER is from .DE then prioritise .DE domains first (???)
...please add. This is more complex then you may think.
The text was updated successfully, but these errors were encountered:
ignore records for isp and cloud ip ranges. ex: ec2-54-254-114-60.ap-1.compute.amazonaws.com. or static-100-38-144-198.nycmny.fios.verizon.net, these have little to no value.
build a domain ranking/scoring algorithm ourselves which takes the following into account:
tld popularity
tld avg cost
length of the domain name
the subdomain level ( ex: a.b.c.com - level 4)
whether a domain belongs to a cloud provider / free hosting provider
Show the 'relevant' domains to the user first.
The tricky part is to determine what is relevant (and this needs discussing) (and all after the pattern/regex-filter was applied)
The text was updated successfully, but these errors were encountered: