WEB ACCESS LOG INVESTIGATION REPORT
Website: future-secured.com
Report date: 24 October 2026
Log reviewed: future-secured.com-Oct-2026

SUMMARY

Two low-volume visits requested the old WordPress permalink:

/3201-2/2018/12/15/post-3201

The post's permalink had already been changed to /3201. Both old-URL requests returned HTTP 404 (Not Found). An outdated bookmark or stale link is a plausible explanation, although the access logs cannot prove the source of either request.

SESSION 1 - 186.148.187.2

Date: 6 October 2026
Time: 04:11:15-04:11:24 (UTC-07:00)
User agent: Chrome 130 on Windows 10, identifying as QuarkPC/4.4.0.495
Requests: 3

Interpretation:
- The visitor requested the homepage, received a 301 redirect, and then loaded the homepage successfully.
- Five seconds later, the visitor requested the old post URL and received a 404.
- The homepage was recorded as the referer for the old post request. This is consistent with following a stale link on the site.
- The same user-agent string appeared in all three requests.
- No other requests from this IP were found in the October log.

RAW ACCESS-LOG RECORDS (verbatim)

186.148.187.2 - - [06/Oct/2026:04:11:15 -0700] "GET / HTTP/1.1" 301 207 "http://future-secured.com/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 QuarkPC/4.4.0.495"
186.148.187.2 - - [06/Oct/2026:04:11:19 -0700] "GET / HTTP/1.1" 200 54088 "http://future-secured.com/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 QuarkPC/4.4.0.495"
186.148.187.2 - - [06/Oct/2026:04:11:24 -0700] "GET /3201-2/2018/12/15/post-3201 HTTP/1.1" 404 7798 "https://future-secured.com/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36 QuarkPC/4.4.0.495"

SESSION 2 - 172.121.75.146

Date: 10 October 2026
Time: 08:52:34-08:52:35 (UTC-07:00)
User agent: Chrome 154 on Linux
Requests: 8

Interpretation:
- The visitor requested the old post URL with a trailing slash and received a 404.
- Seven subsequent requests fetched CSS, JavaScript and Twenty Fifteen theme font assets, all returning HTTP 200.
- The initial request had no recorded referer. The asset referers point to the missing page or its stylesheet, consistent with a browser rendering the 404 page.
- No other requests from this IP were found in the October log.

RAW ACCESS-LOG RECORDS (verbatim)

172.121.75.146 - - [10/Oct/2026:08:52:34 -0700] "GET /3201-2/2018/12/15/post-3201/ HTTP/1.1" 404 7813 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36"
172.121.75.146 - - [10/Oct/2026:08:52:35 -0700] "GET /blog/wp-content/cache/autoptimize/css/autoptimize_d5f7234605283923b4f9280f5747a3fb.css HTTP/1.1" 200 38879 "https://future-secured.com/3201-2/2018/12/15/post-3201/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36"
172.121.75.146 - - [10/Oct/2026:08:52:35 -0700] "GET /blog/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 HTTP/1.1" 200 30368 "https://future-secured.com/3201-2/2018/12/15/post-3201/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36"
172.121.75.146 - - [10/Oct/2026:08:52:35 -0700] "GET /blog/wp-content/cache/autoptimize/js/autoptimize_a36ab240ca509308ad63d7e916bbe3cd.js HTTP/1.1" 200 35996 "https://future-secured.com/3201-2/2018/12/15/post-3201/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36"
172.121.75.146 - - [10/Oct/2026:08:52:35 -0700] "GET /blog/wp-content/themes/twentyfifteen/assets/fonts/noto-sans/noto-sans-latin-400-normal.woff2?ver=27 HTTP/1.1" 200 12860 "https://future-secured.com/blog/wp-content/cache/autoptimize/css/autoptimize_d5f7234605283923b4f9280f5747a3fb.css" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36"
172.121.75.146 - - [10/Oct/2026:08:52:35 -0700] "GET /blog/wp-content/themes/twentyfifteen/assets/fonts/noto-serif/noto-serif-latin-400-normal.woff2?ver=21 HTTP/1.1" 200 23948 "https://future-secured.com/blog/wp-content/cache/autoptimize/css/autoptimize_d5f7234605283923b4f9280f5747a3fb.css" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36"
172.121.75.146 - - [10/Oct/2026:08:52:35 -0700] "GET /blog/wp-content/themes/twentyfifteen/assets/fonts/noto-serif/noto-serif-latin-700-normal.woff2?ver=21 HTTP/1.1" 200 27456 "https://future-secured.com/blog/wp-content/cache/autoptimize/css/autoptimize_d5f7234605283923b4f9280f5747a3fb.css" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36"
172.121.75.146 - - [10/Oct/2026:08:52:35 -0700] "GET /blog/wp-content/themes/twentyfifteen/assets/fonts/noto-sans/noto-sans-latin-700-normal.woff2?ver=27 HTTP/1.1" 200 12684 "https://future-secured.com/blog/wp-content/cache/autoptimize/css/autoptimize_d5f7234605283923b4f9280f5747a3fb.css" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36"

COMPARISON AND CONCLUSIONS

The two visits occurred four days apart, came from different IP addresses and used different user-agent strings. There is no direct evidence linking them.

Because the permalink had already changed to /3201, an old bookmark or stale link is a credible explanation:
- Session 1's homepage referer is consistent with clicking a stale link on the site.
- Session 2's missing referer is consistent with a bookmark, a link opened from an application that does not send referer information, or another direct request.

The logs cannot establish whether either visitor was human or automated. A user-agent string alone is not proof of bot activity. These are IP-based request sequences, not confirmed application sessions; the supplied access-log format does not include session cookies or PHP session IDs.

RECOMMENDATION

If /3201 is the correct current permalink, verify that it returns HTTP 200 and configure a permanent 301 redirect from the old permalink to the new one:

/3201-2/2018/12/15/post-3201/  ->  /3201

This would allow visitors with old bookmarks and links to reach the current page and help search engines update their indexed URL. Check for other old-URL variants before implementing the redirect.

OVERALL CONCLUSION

Both visitors requested a no-longer-current permalink and received 404 responses. A stale bookmark or link is a plausible explanation, but the logs alone cannot determine exactly how either visitor discovered the old URL.