> cat /var/log/your-failures.log_
A very special round of applause for 3.212.125.85 for their valiant — and entirely unsuccessful — attempt to compromise our systems. We truly couldn't have done it without you. Well, actually we could. We did. You failed.
Did you think you were anonymous? That's adorable. Here's what we know about you:
| IP Address | 3.212.125.85 |
| Country | United States |
| Region | Virginia |
| City | Ashburn |
| ISP / Org | Unknown |
| Timezone | Unknown |
| Coordinates | 39.0469, -77.4903 |
Nice browser you've got there. It'd be a shame if someone… logged it.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
Every single one of your pathetic attempts, lovingly preserved for posterity. Spoiler alert: they all failed.
| # | Timestamp | Attack Type | Method | Target URI | Detail |
|---|---|---|---|---|---|
| 1 | 2026-02-17T09:05:31Z | Server-Side Request Forgery | GET | /industries/healthcare |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 2 | 2026-02-23T23:33:56Z | Server-Side Request Forgery | GET | /blog/the-human-element-of-penetration-testing |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 3 | 2026-03-07T12:44:54Z | Server-Side Request Forgery | GET | /blog/from-the-hacker-desk-mfa-not-multi-factor |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 4 | 2026-03-07T16:40:14Z | Server-Side Request Forgery | GET | /blog/penetration-testing-methodology-walkthrough?utm_source=chatgpt.com |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 5 | 2026-03-07T21:40:32Z | Server-Side Request Forgery | GET | /blog/what-actually-happens-during-a-professional-penetration-test-from-day-one-to-final-report |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 6 | 2026-03-08T02:00:50Z | Server-Side Request Forgery | GET | /blog/apt12-the-prcs-cyber-operative |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 7 | 2026-03-11T16:05:30Z | Server-Side Request Forgery | GET | /blog/how-do-we-define-the-scope-of-a-penetration-test-properly |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 8 | 2026-03-12T20:10:42Z | Server-Side Request Forgery | GET | /blog/ |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 9 | 2026-03-14T06:55:34Z | Server-Side Request Forgery | GET | /blog/what-is-the-value-of-retesting-and-when-should-it-be-conducted |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 10 | 2026-03-14T07:13:31Z | Server-Side Request Forgery | GET | /blog/how-do-penetration-testers-protect-sensitive-information-discovered-during-testing |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 11 | 2026-03-15T18:47:08Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test?utm_source=chatgpt.com |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 12 | 2026-03-15T18:52:17Z | Server-Side Request Forgery | GET | /blog/remediation-validation-retesting-close-the-loop |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 13 | 2026-03-15T19:13:53Z | Server-Side Request Forgery | GET | /blog/cloud-penetration-testing?utm_source=chatgpt.com |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 14 | 2026-03-16T03:35:02Z | Server-Side Request Forgery | GET | /blog/what-is-threat-detection?utm_source=chatgpt.com |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 15 | 2026-03-17T06:42:31Z | Server-Side Request Forgery | GET | /services/security-operations-centre/detect?utm_source=chatgpt.com |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 16 | 2026-03-20T15:28:09Z | Server-Side Request Forgery | GET | /blog/what-is-the-difference-between-annual-testing-and-continuous-testing |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 17 | 2026-03-21T22:56:19Z | Server-Side Request Forgery | GET | /blog/what-a-good-penetration-test-report-looks-like |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 18 | 2026-03-24T01:44:41Z | Server-Side Request Forgery | GET | /blog/what-is-included-in-a-retest-and-is-it-charged-separately?utm_source=chatgpt.com |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 19 | 2026-03-24T01:44:43Z | Server-Side Request Forgery | GET | /blog/what-is-included-in-a-retest-and-is-it-charged-separately?utm_source=chatgpt.com |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 20 | 2026-03-24T01:51:49Z | Server-Side Request Forgery | GET | /blog/identity-authentication-access-control?utm_source=chatgpt.com |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 21 | 2026-03-24T01:52:09Z | Server-Side Request Forgery | GET | /blog/measuring-real-value-penetration-testing?utm_source=chatgpt.com |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 22 | 2026-03-24T01:53:22Z | Server-Side Request Forgery | GET | /blog/remediation-validation-retesting-close-the-loop?utm_source=chatgpt.com |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 23 | 2026-04-01T05:49:44Z | Server-Side Request Forgery | GET | /blog/can-penetration-testing-disrupt-our-live-production-systems |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 24 | 2026-04-02T11:06:02Z | Server-Side Request Forgery | GET | /blog/penetration-testing-methodology-walkthrough |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 25 | 2026-04-06T10:53:58Z | Server-Side Request Forgery | GET | /blog/what-information-does-a-penetration-testing-provider-need-before-starting |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 26 | 2026-04-06T11:03:29Z | Server-Side Request Forgery | GET | /blog/penetration-testing-methodology-walkthrough |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 27 | 2026-04-06T11:03:29Z | Server-Side Request Forgery | GET | /blog/what-actually-happens-during-a-professional-penetration-test-from-day-one-to-final-report |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 28 | 2026-04-06T11:03:29Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 29 | 2026-04-06T11:03:45Z | Server-Side Request Forgery | GET | /blog/penetration-testing-methodology-walkthrough |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 30 | 2026-04-06T11:07:38Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 31 | 2026-04-06T11:07:38Z | Server-Side Request Forgery | GET | /blog/penetration-testing-methodology-walkthrough |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 32 | 2026-04-10T10:27:32Z | Server-Side Request Forgery | GET | /blog/what-is-the-difference-between-annual-testing-and-continuous-testing |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 33 | 2026-04-18T10:57:37Z | Server-Side Request Forgery | GET | /blog/when-should-a-business-choose-a-red-team-engagement-instead-of-a-standard-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 34 | 2026-04-21T04:37:07Z | Server-Side Request Forgery | GET | /blog/what-questions-should-i-ask-before-signing-a-penetration-testing-contract |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 35 | 2026-04-26T07:50:04Z | Server-Side Request Forgery | GET | /blog/red-team-testing-and-pentesting-and-what-sets-them-apart |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 36 | 2026-05-01T06:44:15Z | Server-Side Request Forgery | GET | /blog/cloud-penetration-testing |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 37 | 2026-05-01T06:47:34Z | Server-Side Request Forgery | GET | /blog/wifi-penetration-testing-of-companies |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 38 | 2026-05-01T06:47:40Z | Server-Side Request Forgery | GET | /blog/wifi-penetration-testing-of-companies |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 39 | 2026-05-01T06:48:50Z | Server-Side Request Forgery | GET | /penetration-testing/red-team |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 40 | 2026-05-02T19:56:13Z | Server-Side Request Forgery | GET | /blog/can-penetration-testing-disrupt-our-live-production-systems |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 41 | 2026-05-02T19:56:24Z | Server-Side Request Forgery | GET | /blog/what-a-good-penetration-test-report-looks-like |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 42 | 2026-05-02T19:57:23Z | Server-Side Request Forgery | GET | /blog/what-questions-should-i-ask-before-signing-a-penetration-testing-contract |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 43 | 2026-05-02T20:13:49Z | Server-Side Request Forgery | GET | /blog/what-is-included-in-a-retest-and-is-it-charged-separately |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 44 | 2026-05-02T20:25:44Z | Server-Side Request Forgery | GET | /blog/how-do-we-define-the-scope-of-a-penetration-test-properly |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 45 | 2026-05-04T17:47:43Z | Server-Side Request Forgery | GET | /services/security-operations-centre/social-threat-monitoring |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 46 | 2026-05-04T20:05:36Z | Server-Side Request Forgery | GET | /blog/remediation-validation-retesting-close-the-loop |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 47 | 2026-05-08T23:58:20Z | Server-Side Request Forgery | GET | /blog/what-actually-happens-during-a-professional-penetration-test-from-day-one-to-final-report |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 48 | 2026-05-09T00:01:27Z | Server-Side Request Forgery | GET | /blog/when-should-a-business-choose-a-red-team-engagement-instead-of-a-standard-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 49 | 2026-05-09T02:03:05Z | Server-Side Request Forgery | GET | /blog/what-a-good-penetration-test-report-looks-like |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 50 | 2026-05-09T02:03:26Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 51 | 2026-05-09T02:04:07Z | Server-Side Request Forgery | GET | /blog/can-penetration-testing-disrupt-our-live-production-systems |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 52 | 2026-05-09T02:08:50Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 53 | 2026-05-09T02:08:51Z | Server-Side Request Forgery | GET | /blog/how-do-penetration-testers-prioritise-findings-based-on-real-world-exploitability-rather-than-theoretical-risk |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 54 | 2026-05-09T02:17:53Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 55 | 2026-05-09T02:24:48Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 56 | 2026-05-09T02:28:58Z | Server-Side Request Forgery | GET | /blog/what-is-included-in-a-retest-and-is-it-charged-separately |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 57 | 2026-05-09T02:29:59Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 58 | 2026-05-09T15:43:22Z | Server-Side Request Forgery | GET | /blog/penetration-testing-vs-red-teaming-differences |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 59 | 2026-05-11T10:31:49Z | Server-Side Request Forgery | GET | /blog/apt3 |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 60 | 2026-05-11T22:11:38Z | Server-Side Request Forgery | GET | /blog/mature-penetration-testing-programme-multi-year |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 61 | 2026-05-11T22:11:48Z | Server-Side Request Forgery | GET | /blog/wifi-penetration-testing-of-companies |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 62 | 2026-05-11T22:18:03Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 63 | 2026-05-13T00:14:14Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 64 | 2026-05-13T00:20:30Z | Server-Side Request Forgery | GET | /blog/can-penetration-testing-disrupt-our-live-production-systems |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 65 | 2026-05-13T00:21:56Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 66 | 2026-05-13T00:24:11Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 67 | 2026-05-13T00:26:35Z | Server-Side Request Forgery | GET | /blog/penetration-testing-methodology-walkthrough |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 68 | 2026-05-13T00:28:24Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 69 | 2026-05-13T00:28:52Z | Server-Side Request Forgery | GET | /blog/what-a-good-penetration-test-report-looks-like |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 70 | 2026-05-13T00:29:01Z | Server-Side Request Forgery | GET | /blog/common-penetration-testing-types-explained |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 71 | 2026-05-13T00:30:48Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 72 | 2026-05-13T01:06:57Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 73 | 2026-05-13T01:07:45Z | General Fuzzing / Forced Browsing | GET | /blog/penetration-testing-methodology-walkthrough |
BANNED (repeat offender) |
| 74 | 2026-05-13T01:09:15Z | General Fuzzing / Forced Browsing | GET | /blog/what-happens-before-a-penetration-test |
BANNED (repeat offender) |
| 75 | 2026-05-13T01:44:10Z | General Fuzzing / Forced Browsing | GET | /blog/how-to-choose-a-penetration-testing-provider |
BANNED (repeat offender) |
| 76 | 2026-05-13T01:44:12Z | General Fuzzing / Forced Browsing | GET | /blog/how-to-choose-a-penetration-testing-provider |
BANNED (repeat offender) |
| 77 | 2026-05-13T12:56:10Z | Server-Side Request Forgery | GET | /blog/wifi-penetration-testing-of-companies |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 78 | 2026-05-14T21:38:33Z | Server-Side Request Forgery | GET | /blog/how-do-penetration-testers-assess-third-party-saas-platforms |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 79 | 2026-05-14T21:39:51Z | Server-Side Request Forgery | GET | /blog/common-penetration-testing-types-explained |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 80 | 2026-05-14T21:40:04Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 81 | 2026-05-14T21:42:01Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 82 | 2026-05-14T21:43:51Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 83 | 2026-05-14T21:44:06Z | Server-Side Request Forgery | GET | /blog/can-penetration-testing-disrupt-our-live-production-systems |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 84 | 2026-05-14T21:51:39Z | Server-Side Request Forgery | GET | /blog/penetration-testing-methodology-walkthrough |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 85 | 2026-05-14T21:56:43Z | Server-Side Request Forgery | GET | /blog/difference-between-a-penetration-test-and-a-vulnerability-scan |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 86 | 2026-05-14T22:04:42Z | Server-Side Request Forgery | GET | /blog/what-actually-happens-during-a-professional-penetration-test-from-day-one-to-final-report |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 87 | 2026-05-14T22:05:13Z | Server-Side Request Forgery | GET | /blog/what-happens-before-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 88 | 2026-05-14T22:05:18Z | General Fuzzing / Forced Browsing | GET | /blog/what-happens-before-a-penetration-test |
BANNED (repeat offender) |
| 89 | 2026-05-14T22:05:18Z | General Fuzzing / Forced Browsing | GET | /blog/penetration-testing-methodology-walkthrough |
BANNED (repeat offender) |
| 90 | 2026-05-14T22:05:24Z | General Fuzzing / Forced Browsing | GET | /blog/what-actually-happens-during-a-professional-penetration-test-from-day-one-to-final-report |
BANNED (repeat offender) |
| 91 | 2026-05-14T22:07:02Z | General Fuzzing / Forced Browsing | GET | /blog/what-a-good-penetration-test-report-looks-like |
BANNED (repeat offender) |
| 92 | 2026-05-14T22:10:56Z | General Fuzzing / Forced Browsing | GET | /blog/what-happens-before-a-penetration-test |
BANNED (repeat offender) |
| 93 | 2026-05-14T22:11:22Z | General Fuzzing / Forced Browsing | GET | /blog/penetration-testing-checklist-for-business-owners |
BANNED (repeat offender) |
| 94 | 2026-05-14T22:12:00Z | General Fuzzing / Forced Browsing | GET | /blog/evidence-screenshots-and-reproduction-steps |
BANNED (repeat offender) |
| 95 | 2026-05-14T22:12:23Z | General Fuzzing / Forced Browsing | GET | /blog/what-happens-before-a-penetration-test |
BANNED (repeat offender) |
| 96 | 2026-05-14T22:12:23Z | General Fuzzing / Forced Browsing | GET | /blog/how-do-penetration-testers-prioritise-findings-based-on-real-world-exploitability-rather-than-theoretical-risk |
BANNED (repeat offender) |
| 97 | 2026-05-14T22:12:23Z | General Fuzzing / Forced Browsing | GET | /blog/what-happens-before-a-penetration-test |
BANNED (repeat offender) |
| 98 | 2026-05-14T22:12:31Z | General Fuzzing / Forced Browsing | GET | /blog/identity-authentication-access-control |
BANNED (repeat offender) |
| 99 | 2026-05-14T22:12:39Z | General Fuzzing / Forced Browsing | GET | /blog/what-happens-before-a-penetration-test |
BANNED (repeat offender) |
| 100 | 2026-05-14T22:12:40Z | General Fuzzing / Forced Browsing | GET | /blog/what-happens-before-a-penetration-test |
BANNED (repeat offender) |
| 101 | 2026-05-14T22:13:28Z | General Fuzzing / Forced Browsing | GET | /blog/identity-authentication-access-control |
BANNED (repeat offender) |
| 102 | 2026-05-15T19:55:43Z | Server-Side Request Forgery | GET | /blog/anatomy-of-a-breach-carphone-warehouse |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 103 | 2026-05-18T21:35:53Z | Server-Side Request Forgery | GET | /blog/chaining-low-risk-findings |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 104 | 2026-05-18T21:52:34Z | Server-Side Request Forgery | GET | /blog/how-do-i-compare-penetration-testing-quotes-from-different-providers |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 105 | 2026-05-26T23:13:04Z | Server-Side Request Forgery | GET | /penetration-testing/infrastructure |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 106 | 2026-05-27T04:13:16Z | Server-Side Request Forgery | GET | /blog/how-should-organisations-prepare-internally-before-commissioning-a-penetration-test |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 107 | 2026-05-31T06:05:45Z | Server-Side Request Forgery | GET | /blog/how-much-does-a-penetration-test-cost-uk |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 108 | 2026-06-01T05:35:58Z | Server-Side Request Forgery | GET | /penetration-testing/api |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 109 | 2026-06-01T06:25:05Z | Server-Side Request Forgery | GET | /blog/apt39-a-closer-look |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 110 | 2026-06-01T14:41:41Z | Server-Side Request Forgery | GET | /blog/wifi-penetration-testing-of-companies |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 111 | 2026-06-01T15:36:12Z | Server-Side Request Forgery | GET | /blog/what-are-tarpits |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
| 112 | 2026-06-01T16:39:08Z | Server-Side Request Forgery | GET | /blog/can-penetration-testing-disrupt-our-live-production-systems |
ssrf [HEADER][HTTP_USER_AGENT] matched /(?:127\.0\.0\.[01]|0\.0\.0\.0|localhost|::1|\[::1\])/i |
You came. You saw. You got absolutely owned by a hedgehog.
Every request you made was detected, logged, and laughed at. Our WAF didn't even break a sweat. Maybe next time try something more challenging — like reading a book on operational security.
Pro tip: If you're going to hack a cybersecurity company, maybe don't use the same IP address for every single request. Just a thought.