rapiddns

Founder of RapidDNS 🌐 | Building the ultimate recon database with 10Billion+ records. Empowering Bug Bounty Hunters & Red Teams with lightning-fast APIs & CLI.

[rapiddns @rapiddns]

A historic milestone: RapidDNS has officially crossed 10 Billion DNS records!
​To power our next chapter, a major architectural refactoring is underway. Expect unprecedented stability, faster queries, expanded data, new features, and an elevated UX.

[Orange Tsai 🍊 @orange_8361]

Just dropped a new blog post! 🔥

https://t.co/OeVWg1Abw5

[DEVCORE @d3vc0r3]

Orange Tsai (@orange_8361) is taking the #HEXACON2026 stage on Oct 16 in Paris with the logic-only Microsoft Edge full chain he used at #Pwn2Own Berlin 2026.🍊🏆
Five logic bugs, chained. No renderer bugs, no memory corruption, no AI, no collisions.

[/r/netsec @_r_netsec]

Google paid me $90,000 for this RCE https://t.co/yxEkplGbuz

[Ahmed Abdelbaset @r9Mody]

New SQLi technique (concatenation):

`'||Column_name--+`

Then:

`'||table_name.column_name--+` using dot notation.

So:

`'||not_valid_column_name--+` → returns an error
`'||valid_column_name--+` → success
`'||valid_table.valid_column--+` → success

I got a bounty for this f*king sample POC cause akamai and backend limited it to 8 chars. I was lucky because the column name was `id`
on @Bugcrowd
#bugbounty #bugbountytips

[Brut 🇮🇳 @wtf_yodhha]

🚨Bug Bounty Tip: Testing password-reset APIs? Try newline injection in JSON

{"email":"[email protected]\[email protected]"}

✅Join https://t.co/nV1yv5HAhK

If reset links reach both emails, you may have a parameter parsing/input validation flaw worth investigating.

#BugBounty

[rapiddns @rapiddns]

New Version, Coming soon!

#RapidDNS #Recon #OSINT #DNS

[Dragons Community 🪽 @DragonsCyberHQ]

You probably don’t need another recon tool.

But you should bookmark this one.

RapidDNS lets you:

→ Discover subdomains
→ Reverse-search IPs & CIDRs
→ Find domains hosted on an IP
→ Explore A, AAAA, CNAME & MX records
→ Dig through massive DNS datasets
Simple. Fast. Extremely useful for OSINT & recon.
Bookmark it. You’ll need it later. 🔖
👇

[rapiddns @rapiddns]

@ismaeltechI edge for android

[rapiddns @rapiddns]

Big news! We got https://t.co/DbPVbk2Kb9. 🌐 It is officially live and ready for your access today. Go check it out! 🚀 #RapidDNS #InfoSec #recon #bugbounty

[rapiddns @rapiddns]

How I built an AI bug-hunting workflow — and it earned me a real bounty.
Here's how
🔗 https://t.co/1CgZTjlE3o

#BugBounty #AI #bugbountytips #security #openai #gpt

[rapiddns @rapiddns]

RapidDNS lifetime plan closes permanently at July 1, 2026 01:00 UTC. Monthly & annual plans remain. Domain + IP monitoring coming soon for Max. → https://t.co/CTdvjN2TcL

[SunSec @1nf0s3cpt]

🔥Just open-sourced: llm-sast-scanner skill.
Supports 34 vulnerability categories.

Your AI coding agent already knows how to find vulnerabilities. It just doesn’t know where to look, what to trace, or when to stop flagging false positives.

So I gave it a structured SAST workflow: source mapping, taint tracing, and a Judge verification step.

Benchmarks:
F1 = 0.991 (Claude Opus 4.6)
F1 = 0.954 (GPT-5.4)

👇Contributions are welcome to help improve detection rates!
#Claude #Codex #Skills #SAST

[rapiddns @rapiddns]

New OpenClaw skill: RapidDNS

Search subdomains, reverse IPs, enumerate CIDRs — all from your AI assistant.

Built on https://t.co/11fvDW8SRb (https://t.co/Bay3WBLDe6) API. Cross-platform.

clawhub install rapiddns

Upgrade to Pro or Max membership to unlock full features: https://t.co/YcXXklWIXB

#OpenClaw #RapidDNS #bugbountytips #BugBounty #OSINT

[Thariq @trq212]

https://t.co/45C3gKydTK

[Elon Musk @elonmusk]

𝕏 Money early public access will launch next month

[Elon Musk @elonmusk]

𝕏 Money

[Gospel @4osp3l]

0xJS is an AI-powered JS security tool;
- it can identify API keys, and other medium to critical severity secrets with high accuracy.
- also scans for potential security issues in JS i.e DOM-XSS, postMessage, URL redirect. e..t..c
- e..t..c; 0xJS v4.0 ( https://t.co/dfK8dxXdXL )

[rapiddns @rapiddns]

@jack @blocks Proactively embracing change is the only way to avoid being left behind by this rapidly evolving era.

[rapiddns @rapiddns]

Proactively embracing change is the only way to avoid being left behind by this rapidly evolving era.

[jack @jack]

we're making @blocks smaller today. here's my note to the company.

####

today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone.

first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay.

we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly.

i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures.

a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers.

we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold.

to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward.

to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow.

jack