{"id":23909,"date":"2026-10-30T02:21:38","date_gmt":"2026-10-30T02:21:38","guid":{"rendered":"https:\/\/www.hostinger.com\/support\/?p=23909"},"modified":"2026-11-06T08:10:55","modified_gmt":"2026-11-06T08:10:55","slug":"how-to-identify-and-fix-loopback-requests-at-hostinger","status":"publish","type":"post","link":"https:\/\/www.hostinger.com\/support\/how-to-identify-and-fix-loopback-requests-at-hostinger\/","title":{"rendered":"How to identify and fix loopback requests at Hostinger"},"content":{"rendered":"<p>To fix loopback requests on your Hostinger website, find the requests your hosting IP address sends to your own website on the <b>Traffic<\/b> page of the Hostinger dashboard, then stop the process behind them. Loopback requests are HTTP requests a website sends to itself through its own domain, hosting IP address, or localhost.<\/p><p>WordPress uses loopback requests for WP-Cron, the Heartbeat API, Site Health tests, and XML-RPC. Too many loopback requests raise CPU usage and cause slow pages or 503 errors. The most common fixes are replacing WP-Cron with a Hostinger cron job, limiting the Heartbeat API, blocking <code>xmlrpc.php<\/code>, and rescheduling plugin scans. Excessive loopback traffic is a different issue from the WordPress Site Health warning that your site could not complete a loopback request.<\/p><h3><b>Before you start<\/b><\/h3><ul>\n<li>Use a web, cloud, or Agency Hosting plan with access to the <b>Traffic<\/b> page in the Hostinger dashboard.<\/li>\n<li>Find your hosting IP address by following <a data-click-id=\"hgr-post-content-link-how-to-find-your-hostinger-hosting-ip-address\" href=\"https:\/\/www.hostinger.com\/support\/4407303-where-to-find-the-a-record-of-your-hosting-plan-at-hostinger\/\">How to find your Hostinger hosting IP address<\/a>.<\/li>\n<\/ul><h2 id=\"h-how-loopback-requests-affect-your-website-and-resource-usage\">How loopback requests affect your website and resource usage<\/h2><p>Each loopback request runs your website&rsquo;s code on your hosting plan, so a high volume of loopback requests consumes CPU and entry processes. When loopback requests reach your hosting plan&rsquo;s limits, your website loads slowly or returns <a data-click-id=\"hgr-post-content-link-503-errors\" href=\"https:\/\/www.hostinger.com\/support\/3417446-how-to-fix-the-503-error-at-hostinger\/\">503 errors<\/a>.<\/p><p>Loopback requests usually come from a WordPress process that runs too often, such as a stuck WP-Cron job or a backup plugin that scans constantly. Check your CPU and entry process graphs on the <a data-click-id=\"hgr-post-content-link-resources-usage-page\" href=\"https:\/\/www.hostinger.com\/support\/2436138-how-to-check-resource-usage-in-hostinger\/\">Resources Usage page<\/a> to confirm whether your website is close to its limits. On Agency Hosting plans, follow <a data-click-id=\"hgr-post-content-link-how-to-check-resource-usage-in-agency-plan\" href=\"https:\/\/www.hostinger.com\/support\/how-to-check-resource-usage-in-agency-plan\/\">How to check resource usage in Agency plan<\/a> instead.<\/p><h2 id=\"h-identify-loopback-requests-on-the-hostinger-dashboard-traffic-page\">Identify loopback requests on the Hostinger dashboard Traffic page<\/h2><p>Loopback requests appear on the <b>Traffic<\/b> page of the Hostinger dashboard as repeated requests from your own hosting IP address. Follow these steps to find them and the process that sends them:<\/p><ol>\n<li>In the Hostinger dashboard, go to <b>Websites<\/b> and open the <a data-click-id=\"hgr-post-content-link-hosting-dashboard\" href=\"https:\/\/www.hostinger.com\/support\/6627955-how-to-use-the-hosting-dashboard-in-hostinger\/\">hosting dashboard<\/a> of your website.<\/li>\n<li>Select <b>Analytics<\/b> &rarr; <b>Traffic<\/b> on the left sidebar.<\/li>\n<li>Choose a date range under <b>Filter by<\/b>, such as <b>Last 24 hours<\/b> or <b>Last 7 days<\/b>.<\/li>\n<li>In the <b>Top list<\/b>, select <b>IP Addresses<\/b> and check whether your hosting IP address, or an IPv6 address, is among the IP addresses with the most requests.<\/li>\n<li>Open the <b>Access logs<\/b> tab and enter your hosting IP address, for example <code>185.185.185.185<\/code>, in the search bar.<\/li>\n<li>Check the <b>Request<\/b> column for the path that receives repeated requests, such as <code>\/wp-cron.php?doing_wp_cron<\/code>.<br>\n<img decoding=\"async\" class=\"alignnone size-full wp-image-23912\" src=\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-30_08-51.png\" alt=\"\" width=\"1462\" height=\"727\" srcset=\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-30_08-51.png 1462w, https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-30_08-51-300x149.png 300w, https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-30_08-51-1024x509.png 1024w, https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-30_08-51-768x382.png 768w\" sizes=\"(max-width: 1462px) 100vw, 1462px\" \/><\/li>\n<\/ol><p>WordPress loopback requests show a <b>Device<\/b> value in the format <code>WordPress\/[version]; https:\/\/domain.tld<\/code>. Match the path in the <b>Request<\/b> column to the causes in the next section to find the right fix.<\/p><p><b>NOTES<\/b><\/p><ul>\n<li>When Hostinger CDN is active, the <b>IP Address<\/b> column can show CDN IP addresses instead of the real source. Read <a data-click-id=\"hgr-post-content-link-hostinger-cdn-visitor-ip-addresses-in-logs-and-analytics\" href=\"https:\/\/www.hostinger.com\/support\/hostinger-cdn-visitor-ip-addresses-in-logs-and-analytics\/\">Hostinger CDN: Visitor IP addresses in logs and analytics<\/a> for details.<\/li>\n<\/ul><h3>Identify loopback requests from a Hostinger IPv6 address<\/h3><p>Loopback requests sometimes come from an IPv6 address, such as <code>2345:b1b0:6789:20::12a<\/code>, instead of your hosting IPv4 address. A Hostinger IPv6 address doesn&rsquo;t match the IPv4 address in your hosting plan details, so it can look like an unknown visitor. Confirm that an IPv6 address belongs to Hostinger:<\/p><ol>\n<li>Copy the IPv6 address from the <b>Top list<\/b> or the <b>IP address<\/b> column of the <b>Access logs<\/b> tab.<\/li>\n<li>Enter the IPv6 address in an IP lookup tool.<\/li>\n<li>Check that the ISP is <b>Hostinger International Limited<\/b>.<br>\n<img decoding=\"async\" class=\"alignnone size-full wp-image-23922\" src=\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-30_09-10.png\" alt=\"\" width=\"1016\" height=\"647\" srcset=\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-30_09-10.png 1016w, https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-30_09-10-300x191.png 300w, https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-30_09-10-768x489.png 768w\" sizes=\"(max-width: 1016px) 100vw, 1016px\" \/><\/li>\n<li>Search the IPv6 address in the <b>Access logs<\/b> search bar to review the paths it requests.<\/li>\n<\/ol><p>WordPress loopback requests from a Hostinger IPv6 address show the same <b>Device<\/b> value, <code>WordPress\/[version]; https:\/\/domain.tld<\/code>.<\/p><h2 id=\"h-fix-common-causes-of-loopback-requests-on-a-hostinger-website\">Fix common causes of loopback requests on a Hostinger website<\/h2><p>The path in the <b>Request<\/b> column of the access logs shows which process sends the loopback requests. There are five common causes: WP-Cron, the WordPress Heartbeat API, XML-RPC, Site Health REST API checks, and backup or security plugin scans.<\/p><div class=\"intercom-interblocks-table-container\">\n<table role=\"presentation\">\n<tbody>\n<tr>\n<td style=\"background-color: #e3e7fa80;width: 261px\">\n<p class=\"intercom-align-center no-margin\"><b>Request path<\/b><\/p>\n<\/td>\n<td style=\"background-color: #e3e7fa80\">\n<p class=\"intercom-align-center no-margin\"><b>Cause<\/b><\/p>\n<\/td>\n<td style=\"background-color: #e3e7fa80\">\n<p class=\"intercom-align-center no-margin\"><b>Fix<\/b><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 261px\">\n<p class=\"no-margin\"><code>\/wp-cron.php?doing_wp_cron<\/code><\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">A stuck or overly frequent WP-Cron job.<\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">Disable WP-Cron and replace it with a Hostinger cron job.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 261px\">\n<p class=\"no-margin\"><code>\/wp-admin\/admin-ajax.php?action=heartbeat<\/code><\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">Too many WordPress Heartbeat API requests.<\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">Limit or disable the Heartbeat API with a Heartbeat control plugin.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 261px\">\n<p class=\"no-margin\"><code>\/xmlrpc.php<\/code><\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">Pingbacks and trackbacks.<\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">Block <code>xmlrpc.php<\/code> in <code>.htaccess<\/code>, or disable pingbacks.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 261px\">\n<p class=\"no-margin\"><code>\/wp-json\/wp\/v2\/<\/code><\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">A Site Health check loop caused by a plugin blocking REST API requests.<\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">Find the security or caching plugin that blocks the REST API.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 261px\">\n<p class=\"no-margin\"><code>\/wp-admin\/admin-ajax.php<\/code><\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">A backup or security plugin that scans constantly.<\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">Pause the scan or backup and reschedule it to off-peak hours.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div><div class=\"intercom-interblocks-callout\" style=\"background-color: #feedaf80;border-color: #fbc91633\">\n<p>Back up <code>wp-config.php<\/code> and <code>.htaccess<\/code> before you edit them. A syntax error in either file can take your website offline.<\/p>\n<\/div><h3>Replace WP-Cron with a Hostinger cron job<\/h3><p>Repeated requests to <code>\/wp-cron.php?doing_wp_cron<\/code> mean WP-Cron, the WordPress internal scheduler, runs too often. Disable WP-Cron and run it from a Hostinger cron job on a fixed schedule instead:<\/p><ol>\n<li>Open the <a data-click-id=\"hgr-post-content-link-websites-configuration-file\" href=\"https:\/\/www.hostinger.com\/support\/3313359-how-to-find-the-website-s-configuration-file-at-hostinger\/\">website&rsquo;s configuration file<\/a>, <code>wp-config.php<\/code>, in File Manager.<\/li>\n<li>Add the following line above the <code>\/* That's all, stop editing! *\/<\/code> line, then click <strong>Deploy<\/strong> in the top-right corner to make the changes live:\n<pre><code>define('DISABLE_WP_CRON', true);<\/code><\/pre>\n<\/li>\n<li>In the Hostinger dashboard, open <b>Cron Jobs<\/b> on your website&rsquo;s sidebar.<\/li>\n<li>Select <b>Custom<\/b> as the <b>Type<\/b>.<\/li>\n<li>Enter the following command in <b>Command to Run<\/b>, replacing <code>domain.tld<\/code> with your domain:\n<pre><code>wget -O \/dev\/null -o \/dev\/null \"https:\/\/domain.tld\/wp-cron.php?doing_wp_cron\"<\/code><\/pre>\n<\/li>\n<li>Set the <b>Schedule<\/b> to run every 15 minutes, then click <b>Save<\/b>.<\/li>\n<li>Review plugins that register frequent or overlapping cron jobs, and deactivate the ones you don&rsquo;t need.<\/li>\n<\/ol><p>Read <a data-click-id=\"hgr-post-content-link-how-to-set-up-a-cron-job-at-hostinger\" href=\"https:\/\/www.hostinger.com\/support\/1583465-how-to-set-up-a-cron-job-at-hostinger\/\">How to set up a cron job at Hostinger<\/a> for more details about the cron job fields.<\/p><h3>Limit the WordPress Heartbeat API<\/h3><p>Repeated requests to <code>\/wp-admin\/admin-ajax.php?action=heartbeat<\/code> come from the WordPress Heartbeat API, which keeps the WordPress Admin area in sync with the server. Reduce how often the Heartbeat API runs:<\/p><ol>\n<li>Install a Heartbeat control plugin in your WordPress Admin area.<\/li>\n<li>Set the Heartbeat interval to 60 seconds, or disable the Heartbeat API on the WordPress Admin area dashboard.<\/li>\n<li>Close the WordPress editor when you aren&rsquo;t using it, because an open editor keeps sending Heartbeat API requests.<\/li>\n<\/ol><h3>Block XML-RPC loopback requests to xmlrpc.php<\/h3><p>Repeated requests to <code>\/xmlrpc.php<\/code> usually come from WordPress pingbacks and trackbacks. Excessive XML-RPC requests overload the CPU and expose your website to spam.<\/p><ul>\n<li>Block <code>xmlrpc.php<\/code> if you don&rsquo;t use pingbacks, Jetpack, or remote publishing apps. Add the following code to the <code>.htaccess<\/code> file in your website&rsquo;s root folder:\n<pre><code>&lt;Files xmlrpc.php&gt;\r\nOrder Deny,Allow\r\nDeny from all\r\n&lt;\/Files&gt;<\/code><\/pre>\n<\/li>\n<li>Keep XML-RPC enabled if you use Jetpack or remote publishing apps, and disable pingbacks and trackbacks in <b>Settings<\/b> &rarr; <b>Discussion<\/b> in the WordPress Admin area instead.<\/li>\n<\/ul><p>Read <a data-click-id=\"hgr-post-content-link-how-to-create-a-htaccess-file-at-hostinger\" href=\"https:\/\/www.hostinger.com\/support\/1583307-how-to-create-an-htaccess-file-at-hostinger\/\">How to create a .htaccess file at Hostinger<\/a> if your website doesn&rsquo;t have this file yet.<\/p><p><b>NOTES<\/b><\/p><ul>\n<li>Agency Hosting plans have <code>.htaccess<\/code> support disabled by default. Turn on the <b>.htaccess support<\/b> toggle for your WordPress website by following <a data-click-id=\"hgr-post-content-link-how-to-enable-htaccess-on-agency-plans\" href=\"https:\/\/www.hostinger.com\/support\/how-to-enable-htaccess-on-agency-plans\/\">How to enable .htaccess on Agency plans<\/a> before you add the XML-RPC rule.<\/li>\n<li>Non-WordPress websites on Agency Hosting plans can&rsquo;t use <code>.htaccess<\/code>. Read <a data-click-id=\"hgr-post-content-link-htaccess-files-in-agency-hosting\" href=\"https:\/\/www.hostinger.com\/support\/htaccess-files-in-agency-hosting\/\">.htaccess files in Agency Hosting<\/a> for Hostinger dashboard alternatives.<\/li>\n<\/ul><h3>Fix WordPress Site Health REST API loopback loops<\/h3><p>Repeated requests to <code>\/wp-json\/wp\/v2\/<\/code> mean WordPress Site Health calls the REST API, fails, and keeps retrying. This loop usually happens when a security or caching plugin blocks WordPress REST API requests. Find and adjust the plugin:<\/p><ol>\n<li>Deactivate your security and caching plugins one at a time until the loopback requests stop.<\/li>\n<li>Reactivate the plugin that caused the loop.<\/li>\n<li>Allowlist the WordPress REST API in that plugin&rsquo;s settings, or reduce its scan frequency.<\/li>\n<li>Check <b>Tools<\/b> &rarr; <b>Site Health<\/b> in the WordPress Admin area for any remaining warnings.<\/li>\n<\/ol><p>Read <a data-click-id=\"hgr-post-content-link-hostinger-wordpress-site-health-troubleshooting\" href=\"https:\/\/www.hostinger.com\/support\/11035915-hostinger-wordpress-site-health-troubleshooting\/\">Hostinger WordPress Site Health troubleshooting<\/a> to resolve other Site Health warnings.<\/p><h3>Reschedule backup and security plugin scans<\/h3><p>Heavy loopback traffic to <code>\/wp-admin\/admin-ajax.php<\/code> without the Heartbeat action usually comes from a backup or security plugin that runs constantly. Reduce the load from the plugin:<\/p><ul>\n<li>Schedule scans and backups during off-peak hours, such as overnight.<\/li>\n<li>Lower the scan frequency, or use incremental backups instead of full hourly backups.<\/li>\n<\/ul><h3>Fix loopback requests from other scripts or non-WordPress websites<\/h3><p>Loopback requests to paths not listed in the table come from your website&rsquo;s own scripts, services, or integrations. These loopback requests also apply to non-WordPress websites. Reduce them with these steps:<\/p><ol>\n<li>Review the scripts or services in the <b>Request<\/b> column of the access logs that make repeated internal calls.<\/li>\n<li>Disable recently added code, plugins, or integrations one at a time to check whether the loopback requests stop.<\/li>\n<li>Set scheduled tasks and uptime monitors to run no more than once every 10&ndash;15 minutes.<\/li>\n<\/ol><h2 id=\"h-identify-loopback-requests-caused-by-malware\">Identify loopback requests caused by malware<\/h2><p>Malware and other malicious scripts can also generate loopback requests from your hosting IP address. There are four common signs that loopback requests come from malware rather than a normal WordPress process:<\/p><div class=\"intercom-interblocks-table-container\">\n<table role=\"presentation\">\n<tbody>\n<tr>\n<td style=\"background-color: #e3e7fa80;width: 261px\">\n<p class=\"intercom-align-center no-margin\"><b>Sign<\/b><\/p>\n<\/td>\n<td style=\"background-color: #e3e7fa80\">\n<p class=\"intercom-align-center no-margin\"><b>How it differs from normal WordPress loopback requests<\/b><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 261px\">\n<p class=\"no-margin\">Repeated requests to unusual file names, such as <code>\/wp-content\/xyz.php<\/code> or <code>\/.well-known\/gate.php<\/code>.<\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">Normal WordPress loopback requests go to <code>wp-cron.php<\/code>, <code>admin-ajax.php<\/code>, or <code>\/wp-json\/<\/code>.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 261px\">\n<p class=\"no-margin\">Request spikes continue after you disable WP-Cron.<\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">A process outside WordPress sends the loopback requests.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 261px\">\n<p class=\"no-margin\">Request parameters such as <code>cmd=<\/code>, <code>shell=<\/code>, <code>exec=<\/code>, or <code>url=<\/code>.<\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">These parameters point to injected code that runs commands or pulls remote code.<\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 261px\">\n<p class=\"no-margin\">Thousands of small POST requests to <code>\/xmlrpc.php<\/code> per hour from your hosting IP address.<\/p>\n<\/td>\n<td>\n<p class=\"no-margin\">Normal pingbacks don&rsquo;t reach this volume, so a compromised pingback or brute-force script is the likely source.<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div><p>Scan your website with the <a data-click-id=\"hgr-post-content-link-hostinger-malware-scanner\" href=\"https:\/\/www.hostinger.com\/support\/6197555-how-to-use-the-malware-scanner-at-hostinger\/\">Hostinger Malware Scanner<\/a> if your loopback requests match any of these signs. Follow <a data-click-id=\"hgr-post-content-link-how-to-fix-a-malware-infected-wordpress-website-at-hostinger\" href=\"https:\/\/www.hostinger.com\/support\/1583339-how-to-fix-a-malware-infected-wordpress-website-at-hostinger\/\">How to fix a malware-infected WordPress website at Hostinger<\/a> to clean the infected files.<\/p><h2 id=\"h-confirm-loopback-requests-have-stopped-on-your-hostinger-website\">Confirm loopback requests have stopped on your Hostinger website<\/h2><p>Monitor your website&rsquo;s resource usage for 24 hours after applying a fix to confirm the loopback requests have stopped. Check these two places:<\/p><ol>\n<li>Open the <b>Resources Usage<\/b> page, or the resource usage page of your Agency Hosting plan, and check that CPU and entry process usage no longer spike.<\/li>\n<li>Search your hosting IP address, or the Hostinger IPv6 address, in the <b>Access logs<\/b> tab again and check that repeated requests to the same path no longer appear.<\/li>\n<\/ol><p>Read <a data-click-id=\"hgr-post-content-link-what-to-do-if-your-hosting-plan-limits-are-reached-in-hostin\" href=\"https:\/\/www.hostinger.com\/support\/1583532-what-to-do-if-your-hosting-plan-limits-are-reached-in-hostinger\/\">What to do if your hosting plan limits are reached in Hostinger<\/a> if your resource usage stays high after the loopback requests stop.<\/p><p>Once the process behind the loopback requests is fixed, your website stops sending repeated requests to itself, CPU usage drops, and pages load without self-request overloads.<\/p><h2 id=\"h-loopback-requests-faq\">Loopback requests FAQ<\/h2><h3>Are loopback requests always a problem?<\/h3><p>No, WordPress needs loopback requests to run WP-Cron, the Heartbeat API, and Site Health tests. Loopback requests become a problem only when their volume raises CPU usage or causes slow pages and 503 errors.<\/p><h3>Will disabling WP-Cron stop scheduled posts and plugin tasks?<\/h3><p>No, scheduled posts and plugin tasks keep running when you replace WP-Cron with a Hostinger cron job. The Hostinger cron job runs <code>wp-cron.php<\/code> on a fixed schedule, such as every 15 minutes.<\/p><h3>Why does my hosting IP address appear in my website&rsquo;s access logs?<\/h3><p>Your hosting IP address appears in the access logs when your website sends requests to itself. Loopback requests can also appear from a Hostinger IPv6 address, which an IP lookup tool shows with the ISP <b>Hostinger International Limited<\/b>. WordPress loopback requests show a <b>Device<\/b> value in the format <code>WordPress\/[version]; https:\/\/domain.tld<\/code>.<\/p><p><b>Additional resources<\/b><\/p><ul>\n<li><a data-click-id=\"hgr-post-content-link-what-is-wordpress-heartbeat-api-and-how-to-manage-it\" href=\"https:\/\/www.hostinger.com\/tutorials\/wordpress-heartbeat\/\">What is WordPress Heartbeat API and how to manage it<\/a><\/li>\n<li><a data-click-id=\"hgr-post-content-link-xmlrpc-php-in-wordpress-what-it-is-and-why-disable-it\" href=\"https:\/\/www.hostinger.com\/tutorials\/xmlrpc-wordpress\/\">xmlrpc.php in WordPress: what it is and why disable it<\/a><\/li>\n<li><a data-click-id=\"hgr-post-content-link-cron-job-a-comprehensive-guide\" href=\"https:\/\/www.hostinger.com\/tutorials\/cron-job\/\">Cron job: a comprehensive guide<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Spot self-requests from your hosting IP in access logs and cut CPU usage.<\/p>\n","protected":false},"author":594,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_content_updated_date":"","include_on_kodee":true,"footnotes":""},"categories":[180],"tags":[],"class_list":["post-23909","post","type-post","status-publish","format-standard","hentry","category-website-troubleshooting"],"hreflangs":[],"include_on_kodee":true,"_links":{"self":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/23909","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/users\/594"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/comments?post=23909"}],"version-history":[{"count":3,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/23909\/revisions"}],"predecessor-version":[{"id":24803,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/23909\/revisions\/24803"}],"wp:attachment":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/media?parent=23909"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/categories?post=23909"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/tags?post=23909"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}