An Italian Magazine on Mac, Hosting and Security

Ondiz is an independent Italian-language magazine that covers Mac hardware, web practice, shared hosting and security. It publishes practical notes on browser performance, 301 redirects and DNS, compromised WordPress installs and hosting migration. Its readership is mostly Mac users, small site publishers and WordPress administrators.

The publication is not a vendor blog and does not sell hosting. It works through cases: an iPhone 4S or iPad 2 on a mobile network, an SSD Vertex 3 fitted to a 2011 MacBook Pro, iOS 5.0.1, an HSPA TIM hotspot used for tethering. The same case-by-case method carries into the web side, where the Italian Mac and hosting magazine compares Chrome and Firefox in an office setting, tests free office suites, and works through the choice between www and non-www, 301 redirects and DNS records. On the security side it has covered the Flashback Trojan on Mac, Little Snitch as a host-level filter, hijacked accounts, compromised WordPress installations, the warning signs of a bad host and the migration that follows.

What does an Italian Mac and hosting magazine actually publish?

Four subject areas recur.

Apple computing and mobile networking. Device-level notes on iPhone 4S, iPad 2 and a 2011 MacBook Pro with an SSD Vertex 3, plus iOS 5.0.1 behaviour and tethering over an HSPA TIM hotspot. The angle is configuration and observed behaviour rather than product announcement.

Web practice and performance. The www versus non-www decision, 301 redirects and DNS, PageSpeed and Lighthouse scores, CDN configuration and compression. These are written as procedures a site owner can repeat.

Security. The Flashback Trojan on Mac, Little Snitch, account compromise, and WordPress installations that have been modified without the owner's knowledge.

Hosting. How to recognise a bad shared host, and how to move a site without losing redirects, mail or search visibility.

The magazine is in Italian, which limits its direct audience outside Italy, but the procedures it documents are not language-specific. A 301 redirect chain behaves the same way on an Italian host and on a German one.

How does it treat browser performance?

Browser comparison on this site is framed around office use, not benchmark scores. The recurring comparison is Chrome against Firefox in an enterprise or small-office context, where the deciding factors are memory use across many open tabs, extension behaviour, update cadence and how each browser handles a managed profile.

Performance work on the web side is tied to measurement. PageSpeed and Lighthouse are used as the reference tools, and the notes connect their findings to concrete changes: image compression, deferring scripts, enabling text compression, and moving static assets to a CDN. The point made repeatedly is that a score is a diagnostic, not a goal. A site can score well and still be slow for a user on a mobile connection if the first response from the origin server is late.

That is where hosting and performance meet. A CDN in front of a slow origin hides part of the problem for cached pages and exposes it for everything else.

What do 301 redirects and DNS choices change for a site?

The www versus non-www question is treated as a decision to be made once and then enforced. Two hostnames serving the same content create duplicate URLs, split link signals and complicate analytics. The fix is a single canonical hostname and a 301 redirect from the other.

Redirects are covered as a chain problem. Each hop adds latency and each hop is a place where a rule can be wrong. A redirect that passes through http to https, then to www, then to a trailing-slash variant costs three round trips before the browser receives any content. The recommended pattern is one hop from any variant to the canonical URL.

DNS is presented as the layer beneath both. Records that point to an old host after a migration, or a TTL set too high before a planned move, are common causes of a site appearing to be down when the origin is fine. Lowering the TTL before a migration and restoring it afterwards is the standard advice.

How are compromised CMS installs detected and handled?

WordPress compromise is the most detailed security thread on the site. The symptoms described are practical: unfamiliar administrator accounts, files with recent modification dates that the owner did not touch, unexpected outbound requests, injected links in templates, and search results that show content the owner never published.

The response sequence is containment first. Take a backup of the compromised state for analysis, then remove the site from public reach or put it behind authentication, then identify the entry point. Common entry points named are outdated plugins, weak administrator credentials, and a shared host where another account on the same server was breached.

Cleaning is not the end of the process. Credentials are rotated, including database users and any API keys stored in configuration files, and the host is asked for access logs covering the period before the compromise. If the logs are unavailable or the host cannot say how the entry happened, that is itself a signal about the host.

Little Snitch appears in this context as a Mac-side tool for observing outbound connections, useful when a developer wants to see what a local installation is contacting.

When should a site move to a different host?

Migration advice on the site starts from signals rather than from a shopping decision. Warning signs of a bad shared host include support that answers slowly or not at all, resource limits that are enforced without notice, unexplained downtime, no access to raw logs, and a control panel that hides the PHP version or the database configuration.

A second category is performance that cannot be fixed at the application level. If a site is already compressed, cached and served through a CDN, and the origin still responds slowly, the host is the remaining variable.

The migration procedure described is ordered. Lower DNS TTL in advance. Copy files and database to the new host and test on a temporary hostname. Verify that redirects, mail records and any subdomains are reproduced. Switch DNS. Keep the old host running until the new one has served traffic without error for a defined period, then cancel.

The recurring caution is about mail. Moving a website without moving its mail records, or moving them in the wrong order, is a common way to lose messages during a migration.

Who is this written for?

The audience is narrow and stated: Mac users, small publishers and people who administer WordPress sites, often without a dedicated systems administrator. The Italian language and the device-level detail, an iPhone 4S, an iPad 2, a 2011 MacBook Pro, place the material in a specific period, but the hosting and security procedures remain current because the underlying mechanisms, DNS, redirects, CMS file permissions, have not changed.