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
As this issue cname based cdn detection #27 suggests, we could change cdncheck behavior to handle dns_resposes. therefore, I suggest this workflow if we just have dns_response
handle dns_response
get ip's from dns_response
check if belongs to the project discovery cdn ip list ( if does return true , cdn_name )
if not, get cnames from dns_response
check if belongs to cname cdn list ( if does return true , cdn_name and add this ip to cdn ip list )
As this issue wappalyzer based cdn detection #28 suggests , we can also handle the tech_detection response to determine if it belongs to a cdn/waf. we could add this scan as well. I suggest this workflow if we have dns_response + http_response.
handle dns_response
get ip's from dns_response
check if belongs to the project discovery cdn ip list ( if does return true , cdn_name )
if not, get cnames from dns_response
check if belongs to cname cdn list ( if does return true , cdn_name and add this ip to cdn ip list )
if not, check http response technologies.
check if any technology belongs to any cdn/waf ( if does return true , cdn_name and add this ip to cdn ip list )
This discussion was converted from issue #30 on April 25, 2023 22:00.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Beta Was this translation helpful? Give feedback.
All reactions