Jo @LidlUS @lidl @LidlGB, didn't knew you now also host fake versions of the New-York Times:

hxxps[:]//baustandards-qs[.]lidl[.]com

Seems a solid subdomain takeover?
Pointing to AWS: 72.144.31[.]24

#subdomaintakeover #itw

☝️ With #bluesky's increasing popularity, #bugbounty hunters can demonstrate the impact of a #SubdomainTakeover in yet another way: if foo[.]example[.]com is vulnerable, you may be able to claim [@]foo[.]example[.]com as your handle. Handy for impersonation and phishing. 😈

https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial

"A Guide To Subdomain Takeovers 2.0"

https://www.hackerone.com/community/guide-subdomain-takeovers

#security #subdomaintakeover #infosec

Found a great #opensource tool to scan sites for a laundry list of vulnerabilities https://github.com/h4r5h1t/webcopilot.

Just used it to scan all my company domains, works great!

The tools integrated into this single app are the same tools "security researchers" use to scan sites for #xss #SQLi #ssrf #crlf #lfi #subdomaintakeover #openredirect, etc. vulnerabilities - into a single CLI tool.

Can also help avoid/confirm those "beg-bounty" situations where a simple misconfiguration is touted as a "critical vulnerability" because someone use a quick scanning tool to determine that sub-domain take-over is possible (very common, not critical, easy to fix), or missing DMARC records are present (which 98% of all Internet sites have issues with, and is very easy to fix) to demand a cash reward so they can "share additional critical vulnerabilities" that aren't a thing - they just want money.

Have fun!