TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Show HN: Squatmon, a domain squatting monitoring system, with new things

9 点作者 ech超过 9 年前

1 comment

ech超过 9 年前
Hi HN<p>a lot has changed since our last Show HN, and i guess it was time to share these change with you.<p>for those who weren&#x27;t here the first time, we try to catch domain squatting using a bunch of techniques we already used when doing it manually, but in a purely automated fashion. your root domain (think &#x27;facebook&#x27;, &#x27;twitter&#x27;, &#x27;ycombinator&#x27;, etc...) gets through blenders that generate variants, that we&#x27;ll gather info on.<p>we now have all the basics in place so i can confidently call it production ready. free accounts are still the same deal, one domain, five TLDs, all present and future generators, whois and dns resolver, plus a few more still in the oven, and one run per week, which should be enough if your needs are not massive and&#x2F;or specific. you also now have paying options for people with more intensive needs, either timing wise (down to one run per day, and one run per 4 hours will be a possibility once i&#x27;m confident 1: we can handle it, 2: it can actually provide value in the real world) or number-of-tlds-wise.<p>notifications! yeap i know it&#x27;s basic, but we now send you a mail when a run is complete, so you don&#x27;t have to bother reloading waiting for that progress bar to reach 100%. a few client asked us about sms notification, but i&#x27;m not sure about multiple notification channels yet.<p>so what&#x27;s next :<p>we have a bunch of stuff that stayed on the backburner while i was working on making the production as autonomous as possible (complete CI&#x2F;CD stack, built with chef, openstack heat, jenkins, the whole shebang) and the other dev was working on ironing the kinks existing when interacting with horrible protocols like whois (for the sake of everyone&#x27;s sanity, i really hope rdap (<a href="http:&#x2F;&#x2F;about.rdap.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;about.rdap.org&#x2F;</a>) gets traction) or misbehaving dns, or just plain old bugs. we&#x27;re now bringing them back on the front of the workbench.<p>parking detection.<p>this one is simple, and everybody will get it, but i noticed a large number of parked domains in resolution runs, so they&#x27;ll be marked as such.<p>automated phishing detection.<p>this has been a major demand so i&#x27;m prototyping a CV system (ab)using ghost.py and opencv to see if i can get something that has a reasonable false positive rate.<p>malware detection.<p>a smaller demand because it&#x27;s already well covered by other products. for the moment paying accounts get access to google safebrowsing, and i have a bunch of threat exchange APIs access ready to enter the quorum. there&#x27;s a lot of datasharing between those, so i don&#x27;t want to generate false positives because of data sharing. i have also been working slowly on PR for cuckoo sandbox that&#x27;ll help me launch fleets of sandboxes in various configuration (hopefully i&#x27;ll have enough variants that the client is able to more or less choose the one that correspond to its production environment to try and catch targeted attacks)<p>keyword prediction based on the root domain.<p>we have a keyword generator that can generate domain variants, think &#x27;cheap-brand&#x27; for &#x27;brand&#x27;, but if you&#x27;re like me you probably can&#x27;t think of a lot of those (i had good success asking marketing guys for ideas). once again AI to the rescue, i&#x27;m tracking which keywords had the most &#x27;success&#x27; in finding resolving variants, which means once i&#x27;m able to establish lexical domains i&#x27;ll be able to offer everyone a &#x27;most likely keyword for this domain&#x27; help to feed the generator.<p>an API!<p>at the very beginning, when dinosaurs roamed the earth and the iphone 5s the cool product of the year, squatmon was just a very large and very ugly python script i used in various recon engagements. as we decided to slap a shiny web interface on it and share it with others, we didn&#x27;t take the time to make an API the first class citizen and the web interface just the reference client implementation. this is a mistake we intend to correct, so any person with an account, free or otherwise can integrate any of the functionality they have access as a part of something bigger. (i have written an example postfix milter that&#x27;s too terribly slow to be used in production, but can participate in the spam score of an email for example)<p>if you have any question, want to report bugs, or anything really, don&#x27;t hesitate to contact me, my email address is in my profile.<p>edit: i&#x27;m terrible and i said one run per month on the free account. it&#x27;s of course one run per week