1c:I[73356,["10933","static/chunks/10933-713dc1c0b1561380.js","94937","static/chunks/94937-3f819e5ef7dfa8a0.js","9131","static/chunks/9131-9372417797d59026.js","98244","static/chunks/98244-037342d518451489.js","6342","static/chunks/6342-5661a6a2702af160.js","27689","static/chunks/27689-8d5be78f17754629.js","34877","static/chunks/app/(marketing)/blog/%5Bslug%5D/page-837e41d662ba9ddc.js"],"BlogArticleEnhancements"] 1d:I[53721,["10933","static/chunks/10933-713dc1c0b1561380.js","94937","static/chunks/94937-3f819e5ef7dfa8a0.js","9131","static/chunks/9131-9372417797d59026.js","98244","static/chunks/98244-037342d518451489.js","6342","static/chunks/6342-5661a6a2702af160.js","27689","static/chunks/27689-8d5be78f17754629.js","34877","static/chunks/app/(marketing)/blog/%5Bslug%5D/page-837e41d662ba9ddc.js"],"BlogViewTracker"] 1f:I[97042,["10933","static/chunks/10933-713dc1c0b1561380.js","94937","static/chunks/94937-3f819e5ef7dfa8a0.js","9131","static/chunks/9131-9372417797d59026.js","98244","static/chunks/98244-037342d518451489.js","6342","static/chunks/6342-5661a6a2702af160.js","27689","static/chunks/27689-8d5be78f17754629.js","34877","static/chunks/app/(marketing)/blog/%5Bslug%5D/page-837e41d662ba9ddc.js"],"BlogToc"] 24:I[54324,[],"IconMark"] :HL["https://codelivly.com/wp-content/uploads/2023/07/My-Recon-methodology-and-tools.png","image"] 20:T7224,

Hey, there! I'm Rocky, your friendly neighborhood bug bounty hunter. Let's take a walk down memory lane and I'll tell you how I stumbled into this wild world of web security and bug bounties.

So, back in the day, I was just another geek, lost in the universe of code, always intrigued by how things worked (or didn't work) in the virtual space. I'd spend hours playing around with different software, but honestly, at that point, it was more about curiosity than anything else.

Then, one fine day, I stumbled upon a blog post about something called a 'bug bounty program'. I was instantly hooked. Here was a way to take my coding and exploring to a new level, helping companies find their weaknesses, making the internet a safer place, and get paid for it? Sign me up!

My initial days in bug bounty hunting were a bit of a whirlwind. I won't lie, there was a steep learning curve. Those late-night reading sessions, countless cups of coffee, and heaps of frustration when I'd hit a wall. But hey, it was all part of the journey, and boy was it worth it!

It didn't take long for me to realize that to be a successful bug bounty hunter, I needed a game plan. A structured, methodical approach to finding and exploiting vulnerabilities. That's how I got into reconnaissance, or as we in the field like to call it, 'recon'. This was the missing piece of the puzzle, the secret sauce to my bug bounty hunting.

And that, my friends, is the super short version of how I landed here. Today, I'm going to peel back the curtain and share my recon methodology and the tools that I use on my bug bounty adventures. Buckle up, and let's get into it!

Understanding Reconnaissance

Alright folks, let's break it down now. If you're fresh to the world of cybersecurity, you might be wondering what the heck is this 'reconnaissance' I keep rambling about. Well, let me enlighten you!

Reconnaissance, or 'recon' for short, is kind of like doing your homework before you go on a big adventure. In the context of bug bounty hunting, it's the process of collecting as much information as possible about a target - say, a website, a system, or an app - before trying to find vulnerabilities in it.

Imagine you're going on a treasure hunt (because, let's face it, that's what bug hunting kinda is). Would you just wander aimlessly around, hoping to stumble upon the gold? Heck no! You'd start by looking at the map, understanding the lay of the land, maybe even doing a bit of research about where treasure is usually hidden. That's what recon is - it's preparing yourself to find the 'treasure', or in our case, the bugs.

Recon can involve anything from scanning open ports on a server to understanding the architecture of a web application, or even something as simple as Googling to find info people have unwittingly left exposed. It's all about gathering intel that can point you to potential vulnerabilities.

So why is recon so dang important in bug bounty hunting? Well, jumping right into the hunt without doing recon is like shooting in the dark. You might hit something, but chances are you'll waste a lot of bullets. Recon helps us aim before we shoot, and increases our chances of hitting the target. Plus, let's be real - it's pretty cool to feel like a detective, uncovering clues and connecting the dots.

So there you have it, a crash course in reconnaissance! Now that we've covered the basics, I'll get into the juicy details of my personal approach to recon in the below section. Stay tuned!

My Recon Philosophy

Okay, we've gotten the basic idea of what recon is, right? Now, let's get into the fun part – my personal philosophy when it comes to recon. Because trust me, not all recon strategies are made equal, and your approach can make a world of difference.

First off, let me tell you, I like to think of myself as a bit of an explorer. Yeah, like Indiana Jones, but with less running from boulders and more running code. My point is, when I do recon, I believe in diving deep. Surface-level stuff just doesn't cut it for me.

I firmly believe that successful recon is all about being meticulous and having patience. You know how you used to get told, "Slow and steady wins the race," back in school? Turns out they weren't just talking about tortoises. In the world of bug hunting, it's the thorough and patient hunters who end up finding the most valuable bugs.

My recon philosophy is a mix of methodical investigation and creative problem solving. I'm all about following a systematic approach - knowing which tools to use, which processes to follow, and leaving no stone unturned. But it's equally important to think outside the box. Sometimes, the most glaring vulnerabilities aren't where you'd expect them to be.

I'm also big on automation, where it makes sense. There are some parts of recon that are repetitive and can be easily automated, freeing up my time for the more complex tasks. But remember, no tool or script can replace human intuition and ingenuity. That's why I always strike a balance between automated processes and manual investigation.

And finally, it's crucial to keep up with the ever-changing landscape of web security. Technology is constantly evolving, and what worked yesterday might not work tomorrow. That's why part of my recon process is always learning, always adapting, and always staying ahead of the game.

In a nutshell, my recon philosophy is to be thorough, patient, creative, balanced, and adaptable. It's not just about finding bugs - it's about being the best bug hunter I can be. Now that you know where I'm coming from, let's dive into the tools I use to put this philosophy into action.

Discover: Reconnaissance: IS IT Really Matter

Essential Tools in My Bag

Alrighty then! We've talked about what recon is and my personal philosophy about it. Now, it's time to peek into my toolkit. You know, like Batman's utility belt, but for bug hunting.

Remember, these tools are not some magical keys to success. They're aids that help me follow my recon process more effectively. So, without further ado, let's jump in.

osint concept in cybersecurity. It describes techniques, risks, or controls that defenders and ethical hackers must understand to protect systems and conduct authorized security testing. Learning Shodan helps you recognize attacks in the wild and apply industry-standard mitigations aligned with frameworks like OWASP and NIST.">Shodan: Shodan is like my very own online spyglass. It's a search engine that lets me find specific types of computers, routers, servers - you name it - connected to the internet. Shodan is insanely useful for discovering devices that may have been overlooked and could provide an entry point to a network.
Burp Suite: Ah, Burp Suite, my trusty sidekick. It's a complete toolkit for web application security testing. From intercepting browser traffic to mapping out a website's attack surface, it does a lot of the heavy lifting. A big shout out to the Repeater and Intruder tools, they've saved my bacon more times than I can count.
Nmap: This one's a classic. Nmap, short for 'Network Mapper', is like a Swiss Army knife for network exploration and security auditing. It helps me scan systems, networks, and find open ports. It's kinda like knocking on all the doors in a building to see which ones are open.
Dirsearch: I use Dirsearch for content discovery, to find those hidden directories or files that the developers might not want me to see. It's like having X-ray vision, but for websites.
Sublist3r: Last but definitely not least, I've got Sublist3r in my toolkit. It's a great tool for enumerating subdomains, which can sometimes house hidden vulnerabilities.

Those are the main tools in my bag, but remember that new tools are being developed all the time. Part of being a good bug hunter is keeping up with the latest and greatest tools in the industry. I also have a bunch of scripts and smaller tools that help with specific tasks, but that's a topic for another day.

Now that we've seen the tools, let's get into how I use them in the wild. Stay tuned for some bug bounty action!

Vulnerability Searching

Okay, so we've got our tools ready, our recon philosophy is in place, and we're raring to go. What's next? The exciting bit - vulnerability searching!

The first thing to remember here is, vulnerability searching isn't about rushing in all guns blazing. Remember my philosophy? We're aiming for a more methodical, patient approach. So, let's break down how I go about hunting for those precious bugs.

Step 1: Know your target: It all starts with a deep understanding of my target. What kind of website or application is it? What technology is it built on? What are its main features and functionalities? These are all important questions that help me get a handle on where vulnerabilities might lie.

Step 2: Mapping the terrain: Next, I like to map out the application's structure and functionalities, often using tools like Burp Suite. This step involves understanding the application flow, identifying all the entry points (like form fields, URL parameters, etc.), and any APIs or services it might be interacting with.

Step 3: Automatic Scanning: Now's the time to bring out the big guns - the automatic scanning tools. I use tools like Burp Suite's Scanner and Nmap to scan the application for common vulnerabilities and open ports. But remember, automatic scanning isn't foolproof. It's a starting point, not the end of the journey.

Step 4: Manual Examination: This is where the human element comes into play. I manually explore the application, playing around with the functionalities, manipulating parameters, trying to trigger unexpected behaviors or errors. It's a bit like a game - how can I trick the application into doing something it's not supposed to do?

Step 5: Digging Deeper: Depending on the target and the potential vulnerabilities, this step might involve more specialized techniques like checking for code injection, testing APIs, assessing the application’s security configurations, and so on. Here, tools like Dirsearch or Sublist3r can be really handy.

Step 6: Reporting and Verification: Once I've found a potential vulnerability, it's not time to pop the champagne yet. It's important to verify the vulnerability, understand its potential impact, and compile a detailed report for the client. Because at the end of the day, the goal isn't just to find bugs, but to help improve the application's security.

That, in a nutshell, is how I go about searching for vulnerabilities. Of course, each hunt is unique and sometimes, you have to think on your feet and adapt your strategy. But having a game plan like this helps ensure that you're not just shooting in the dark, and gets you a step closer to striking gold.

Strategies for Different Web Security Challenges

Time to get into the nitty-gritty, folks. If there's one thing I've learned in my bug bounty adventures, it's that no two targets are the same. You can't expect to use the same exact strategy for every web security challenge and come out on top. You've gotta adapt and think on your feet. So let's discuss some of the strategies I use for different kinds of challenges.

1. For Web Applications:

Web applications are complex beasts, with all sorts of components and functionalities. Here, my strategy usually starts with mapping out the entire application, using tools like Burp Suite. I explore every nook and cranny of the site, checking forms, cookies, headers, API endpoints, and so on. I'm always on the lookout for issues like Cross-Site Scripting (XSS), SQL Injection, and Cross-Site Request Forgery (CSRF), among others.

2. For APIs:

APIs are becoming increasingly popular, and with good reason. But they come with their own set of challenges. My approach here often involves tools like Postman or Burp Suite to send custom requests and observe the responses. I also pay close attention to the API documentation if it's available. Common issues I look for include misconfigurations, insecure endpoints, and improper access controls.

3. For Network Infrastructure:

If I'm dealing with network infrastructure, I switch gears a bit. Tools like Nmap and Shodan become my best friends. I'm scanning for open ports, exposed services, and weak points in the network's defenses. The focus here is usually on issues like open ports, outdated services, or misconfigurations.

4. For Serverless Applications:

With the rise of serverless architecture, new security challenges have emerged. Here, I'm often looking for misconfigurations in the serverless setup. I also look closely at the permissions and access controls, as these can often be a weak point in serverless applications.

5. For Cloud Infrastructure:

When it comes to cloud infrastructures, misconfigurations are the name of the game. Whether it's unsecured storage buckets or overly permissive security groups, there's a lot to look out for. Tools like ScoutSuite can be really useful here.

Remember, these are just starting points. Every challenge will require you to think creatively and come up with new approaches. But having a framework to start from can be a huge help. So don your explorer's hat, and get ready to dive into the fascinating world of web security challenges!

Keeping up with Tech Developments

Alright, let's get real for a sec here. The tech world moves faster than a Ferrari on a straightaway, and web security is no exception. New technologies, vulnerabilities, and techniques are being discovered every day, and if you're not careful, you might find yourself left in the dust.

But don't worry! Your buddy Rocky's got some tips on how to stay up-to-date with all the latest and greatest in tech and web security.

Blogs and Websites: There are a bunch of fantastic blogs and websites out there that share insightful articles and updates on the latest happenings in tech and cybersecurity. Websites like The Hacker News, Krebs on Security, and Dark Reading are just a few examples.

Podcasts: Podcasts are another great way to stay in the loop. They're a great source of information and you can listen to them on the go. Check out podcasts like Darknet Diaries, The CyberWire, or Smashing Security.

Online Courses and Webinars: Websites like Coursera, Udemy, and Cybrary offer a plethora of courses on various topics related to web security. Plus, a lot of organizations and experts host webinars that you can join to learn about the latest techniques and tools.

Conferences and Meetups: Events like DEF CON, Black Hat, or local meetups are fantastic places to learn about the latest in web security, network with other professionals, and even show off your skills in capture the flag (CTF) competitions.

Social Media and Forums: Platforms like Twitter, Reddit, and forums like Stack Exchange are buzzing with discussions on the latest in tech and web security. Just follow the right people or join the right communities, and you'll have a wealth of information at your fingertips.

Continuous Learning and Practice: Lastly, but most importantly, always be learning. Regularly practice your skills, take on new challenges, and don't be afraid to dive into new areas.

Remember, staying up-to-date is not just about knowing the latest buzzwords. It's about continuously improving your skills, adapting to new challenges, and being the best bug bounty hunter you can be. Because as the great Ferris Bueller said, "Life moves pretty fast. If you don't stop and look around once in a while, you could miss it." Same goes for tech and web security, my friends!

Learnings from My Bug Bounty Experiences

Ah, the bug bounty experiences! Let me tell you, each one has been a rollercoaster ride. From sleepless nights staring at code to the thrill of finding a juicy vulnerability, it's been quite a journey. And boy, have I learned a ton along the way!

So, let me share some nuggets of wisdom from my bug bounty adventures.

Patience is Key: This isn't a sprint, it's a marathon. Some bugs are found in a matter of minutes, others might take weeks. Patience is a virtue in this game. Don't get discouraged if you don't find a bug right away. Keep looking, keep learning, and trust the process.

Never Underestimate the Basics: I've found some of my best bugs by just sticking to the basics. Sure, complex vulnerabilities are exciting and challenging, but often it's the basic stuff that gets overlooked. So, don't underestimate the power of the basics.

Knowledge is Power: The more you know, the more bugs you can find. Sounds simple, right? Make sure to always keep learning, expanding your skill set and knowledge base. The broader and deeper your knowledge, the better you'll be at spotting vulnerabilities.

Automation is Your Friend: If I've said it once, I've said it a thousand times. Automation can save you a ton of time and effort. Automate what you can, but remember, automation is a tool, not a substitute for manual testing and intuition.

Reporting Matters: Finding a bug is only half the battle. The other half is reporting it. You need to clearly explain what the bug is, how it can be exploited, and what its potential impact is. A good report can make all the difference between a bug being accepted or rejected.

Networking is Important: The bug bounty community is a goldmine of knowledge and experience. Don't hesitate to connect with other hunters, share your experiences, and learn from theirs. Remember, we're all in this together!

Respect the Rules: Every bug bounty program has its rules and guidelines. Make sure to always respect them. Responsible disclosure is the name of the game, folks!

Enjoy the Journey: Finally, and most importantly, enjoy the process. Yes, bug hunting can be frustrating and challenging. But it's also a lot of fun! So, remember to enjoy the journey, celebrate your victories, and learn from your mistakes.

So, there you have it. Some of my top learnings from my bug bounty journey. Remember, each experience is a chance to learn and grow. So, keep hunting, keep learning, and keep enjoying the ride!

Tips for Aspiring Bug Bounty Hunters

Alright future bug bounty hunters, gather 'round. Your pal Rocky's got some advice for you. Whether you're just thinking about dipping your toes in or you've already started wading into the bug bounty waters, here are a few tips to set you on the right path.

Build Your Skills: First things first, you gotta have a solid understanding of web technologies and security principles. Learn HTML, CSS, JavaScript, and get comfortable with different types of databases. Understand how the web works, from HTTP requests to cookies and sessions.

Start with the Basics: Don't jump into the deep end right away. Start with basic vulnerabilities like XSS, CSRF, SQL injection, and slowly work your way up. Websites like OWASP have fantastic resources to get you started.

Get Hands-On Experience: Knowledge is important, but nothing beats hands-on experience. Play around with tools, try out different techniques, and don't be afraid to break things (in a controlled environment, of course!). Platforms like Hack The Box or TryHackMe are excellent for practice.

Join the Community: The bug bounty community is a treasure trove of knowledge and support. Participate in forums, join discussions on social media, attend meetups and conferences. Don't hesitate to ask questions, and always be ready to learn.

Stay Up-to-Date: Tech is always evolving, and so are the vulnerabilities. Make it a point to stay updated on the latest developments in the field. Read blogs, listen to podcasts, and follow industry experts on social media.

Start Small: When you're ready to start hunting, pick a small, relatively less-known program. They usually have less competition and could be a great place to get your first bounty.

Respect the Rules: Always follow the program's rules and guidelines. This is non-negotiable. Responsible disclosure is what separates a hacker from a criminal.

Don't Get Discouraged: Bug hunting can be challenging and frustrating at times. You might spend days, weeks, even months without finding a bug. That's okay. Don't get discouraged. Keep learning, keep trying, and remember, every failure is just a stepping stone towards success.

Celebrate Your Successes: Finally, don't forget to celebrate your wins, no matter how small. Every bug you find is a testament to your skills and effort. So, pat yourself on the back, do a little happy dance, and then get back to hunting!

Remember, everyone's journey is unique. So, carve out your own path, learn at your own pace, and don't forget to enjoy the ride. Happy hunting, future bug bounty hunters!

And there you have it, my friends. That's the story of my bug bounty journey - the ups, the downs, and everything in between. From my humble beginnings to the countless hours spent staring at lines of code, it's been quite a ride.

But the journey isn't over. Far from it. The world of web security is constantly changing, constantly evolving, and I'm excited to see where it takes me next.

To all my fellow bug bounty hunters out there, keep hunting, keep learning, and most importantly, keep enjoying the ride. We're part of an amazing community, a community that's making the web a safer place, one bug at a time.

And to all you aspiring hunters, I hope my experiences and tips inspire you and guide you on your own bug bounty journey. It's not always going to be easy, there will be challenges and hurdles along the way. But remember, every challenge is a learning opportunity, every hurdle a stepping stone towards success.

So, go forth and conquer, my friends. The web awaits. Happy hunting!

See you in next article .

Signing off for now, Rocky .

9:[["$","$L1c",null,{}],["$","$L1d",null,{"slug":"recon-methodology-and-tools-for-bug-bounty-and-web-security"}],"$L1e",["$","div",null,{"className":"mx-auto max-w-6xl px-4 py-10 sm:px-6 sm:py-12","children":["$","div",null,{"className":"lg:grid lg:grid-cols-[minmax(0,1fr)_320px] lg:gap-10 xl:gap-12","children":[["$","article",null,{"id":"blog-content","className":"blog-content min-w-0 max-w-3xl","children":[["$","nav",null,{"className":"font-mono mb-6 text-xs text-[var(--hm-muted)]","children":[["$","$L1a",null,{"href":"/","className":"text-[var(--hm-muted)] no-underline hover:text-[var(--hm-mint)]","children":"Home"}],["$","span",null,{"className":"mx-2","children":"/"}],["$","$L1a",null,{"href":"/blog","className":"text-[var(--hm-muted)] no-underline hover:text-[var(--hm-mint)]","children":"Blog"}],["$","span",null,{"className":"mx-2","children":"/"}],["$","span",null,{"className":"text-[var(--hm-text)]","children":"My Recon methodology and tools for bug bounty and web security"}]]}],["$","header",null,{"className":"mb-8","children":[["$","div",null,{"className":"mb-6 overflow-hidden rounded-[2px] border border-[var(--hm-border)]","children":["$","img",null,{"src":"https://codelivly.com/wp-content/uploads/2023/07/My-Recon-methodology-and-tools.png","alt":"My Recon methodology and tools for bug bounty and web security","className":"aspect-[16/9] w-full object-cover"}]}],["$","div",null,{"className":"mb-4 flex flex-wrap gap-2","children":[["$","span",null,{"className":"font-mono rounded-[2px] border border-[var(--hm-mint)]/30 bg-[var(--hm-mint)]/10 px-2.5 py-1 text-[11px] uppercase tracking-wider text-[var(--hm-mint)]","children":"Bug Bounty"}],[]]}],["$","h1",null,{"className":"font-display text-3xl font-bold leading-tight tracking-[-0.01em] text-[var(--hm-text-strong)] sm:text-[2.5rem]","children":"My Recon methodology and tools for bug bounty and web security"}],["$","p",null,{"className":"mt-4 text-base leading-relaxed text-[var(--hm-muted)]","children":"Hey, there! I'm Rocky, your friendly neighborhood bug bounty hunter. Let's take a walk down memory lane and I'll tell you how I stumbled into this wild world of web security and bug bounties. So, back"}],["$","div",null,{"className":"mt-5 flex flex-wrap items-center gap-x-3 gap-y-2 border-t border-[var(--hm-border)] pt-5 font-mono text-xs text-[var(--hm-muted)]","children":[["$","span",null,{"className":"flex items-center gap-2","children":[["$","span",null,{"aria-hidden":true,"className":"flex h-7 w-7 items-center justify-center rounded-full border border-[var(--hm-ring)] bg-[rgba(0,230,118,0.08)] text-[11px] font-bold text-[var(--hm-mint)]","children":"R"}],["$","span",null,{"className":"text-[var(--hm-text)]","children":"rocky"}]]}],["$","span",null,{"aria-hidden":true,"children":"·"}],["$","time",null,{"dateTime":"2023-07-13T11:42:01.000Z","children":"Jul 13, 2023"}],[["$","span",null,{"aria-hidden":true,"children":"·"}],["$","span",null,{"children":[19," min read"]}]]]}]]}],["$","$L1f",null,{"items":[{"id":"understanding-reconnaissance","text":"Understanding Reconnaissance","depth":1},{"id":"my-recon-philosophy","text":"My Recon Philosophy","depth":1},{"id":"essential-tools-in-my-bag","text":"Essential Tools in My Bag","depth":1},{"id":"vulnerability-searching","text":"Vulnerability Searching","depth":1},{"id":"strategies-for-different-web-security-challenges","text":"Strategies for Different Web Security Challenges","depth":1},{"id":"keeping-up-with-tech-developments","text":"Keeping up with Tech Developments","depth":1},{"id":"learnings-from-my-bug-bounty-experiences","text":"Learnings from My Bug Bounty Experiences","depth":1},{"id":"tips-for-aspiring-bug-bounty-hunters","text":"Tips for Aspiring Bug Bounty Hunters","depth":1}]}],["$","div",null,{"className":"blog-prose text-base leading-relaxed text-[var(--hm-text)]","children":["$","div",null,{"dangerouslySetInnerHTML":{"__html":"$20"}}]}],false,"$L21","$L22"]}],"$L23"]}]}]] c:null 11:[["$","title","0",{"children":"My Recon methodology and tools for bug bounty and web…"}],["$","meta","1",{"name":"description","content":"Hey, there! I'm Rocky, your friendly neighborhood bug bounty hunter. Let's take a walk down memory lane and I'll tell you how I stumbled into this wild world…"}],["$","meta","2",{"name":"author","content":"Codelivly Team"}],["$","meta","3",{"name":"creator","content":"Codelivly"}],["$","meta","4",{"name":"publisher","content":"Codelivly"}],["$","meta","5",{"name":"robots","content":"index, follow"}],["$","link","6",{"rel":"canonical","href":"https://codelivly.com/recon-methodology-and-tools-for-bug-bounty-and-web-security"}],["$","link","7",{"rel":"alternate","hrefLang":"en-US","href":"https://codelivly.com/recon-methodology-and-tools-for-bug-bounty-and-web-security"}],["$","meta","8",{"property":"og:title","content":"My Recon methodology and tools for bug bounty and web…"}],["$","meta","9",{"property":"og:description","content":"Hey, there! I'm Rocky, your friendly neighborhood bug bounty hunter. Let's take a walk down memory lane and I'll tell you how I stumbled into this wild world…"}],["$","meta","10",{"property":"og:url","content":"https://codelivly.com/recon-methodology-and-tools-for-bug-bounty-and-web-security"}],["$","meta","11",{"property":"og:site_name","content":"Codelivly"}],["$","meta","12",{"property":"og:locale","content":"en_US"}],["$","meta","13",{"property":"og:image","content":"https://codelivly.com/wp-content/uploads/2023/07/My-Recon-methodology-and-tools.png"}],["$","meta","14",{"property":"og:image:width","content":"1200"}],["$","meta","15",{"property":"og:image:height","content":"630"}],["$","meta","16",{"property":"og:type","content":"article"}],["$","meta","17",{"name":"twitter:card","content":"summary_large_image"}],["$","meta","18",{"name":"twitter:creator","content":"@codelivly"}],["$","meta","19",{"name":"twitter:title","content":"My Recon methodology and tools for bug bounty and web…"}],["$","meta","20",{"name":"twitter:description","content":"Hey, there! I'm Rocky, your friendly neighborhood bug bounty hunter. Let's take a walk down memory lane and I'll tell you how I stumbled into this wild world…"}],["$","meta","21",{"name":"twitter:image","content":"https://codelivly.com/wp-content/uploads/2023/07/My-Recon-methodology-and-tools.png"}],["$","link","22",{"rel":"shortcut icon","href":"/favicon.svg"}],["$","link","23",{"rel":"icon","href":"/favicon.svg"}],["$","link","24",{"rel":"apple-touch-icon","href":"/favicon.svg"}],["$","$L24","25",{}]]