Website profiles · Technology insights · Alternatives

mackie100projects.altervista.org

clover, bootloader, opencore, bios, custom, hackintosh, mac, osx, personalize, bootsoftware, themes, uefi, windows, games

Paid content
Visit website
Profile views 0 Outbound visits 0 Normal
mackie100 projects Full homepage screenshot

At a glance

Category
Other
Language
English
Paid-content signal
Paid contentObserved
Registered
2000
Hosting
altervista.orgInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is mackie100 projects?

mackie100 projects is a software release hub for people building and maintaining Hackintosh systems. Its pages are changelogs for two macOS boot-configuration utilities, Clover Configurator and OpenCore Configurator, listing each new version, the date, the notable changes, and a download link. Recent entries show Clover Configurator 5.29.0.0 adding boot, kernel and UEFI quirk keys, and OpenCore Configurator 2.78.2.0 adding support for OpenCore 1.0.8.

Who it is for

  • Hackintosh builders who need a current Configurator version matched to their bootloader release.
  • Troubleshooters checking whether a fix, such as the noted macOS 15.4 bug fix in Clover Configurator 5.28.0.1, applies to them.
  • Returning users who want to see what changed between versions before updating a working setup.

What it is not

The site is a changelog and download index, not a tutorial. It reports version numbers and feature additions but does not explain how to configure quirks or recover a machine that fails to boot after an update.

Practical next step

Before downloading, note your installed bootloader version and read the matching changelog entry. If the entry only adds support for a newer OpenCore release than you run, updating the Configurator alone will not help; align both. For background on OpenCore itself, the official documentation at Dortania is the reference to consult alongside these release notes.

Which Clover Configurator version added the ClearTaskSwitchBit Quirks key?

Clover Configurator version 5.29.0.0 added the ClearTaskSwitchBit key under Quirks → Booter properties, according to the changelog on mackie100 projects. That release also added DisableIoMapperMapping (Quirks → Kernel) and ResizeGpuBars (Quirks → UEFI).

If you maintain an older Clover setup and need that key, treat 5.29.0.0 as the minimum editor version; when updating, check the changelog for the matching OpenCore Configurator release if you also manage an OpenCore config, since the two tools track different bootloader versions.

How do I know which OpenCore Configurator release supports my installed OpenCore version?

Match the Configurator release to the OpenCore version named in its changelog. On mackie100 projects, each OpenCore Configurator entry states the OpenCore version it supports: version 2.78.2.0 supports OpenCore 1.0.8, 2.78.1.0 supports 1.0.6, and 2.78.0.2 supports 1.0.5. If your installed OpenCore version is listed for a release, that release is the intended match.

Practical check

  1. Find your installed OpenCore version (from the OpenCore release you downloaded or your boot files).
  2. Scan the Configurator changelog entries for that exact version.
  3. Pick the newest Configurator entry that names it, then read that entry's notes before applying changes.

A reader running OpenCore 1.0.6, for example, would look for the 2.78.1.0 entry rather than assuming the newest release fits. Newer Configurator builds often target newer OpenCore releases, so guessing can leave you editing keys your OpenCore build doesn't recognise.

For background on OpenCore itself, the official project documentation at Dortania explains version-specific settings, which helps you judge whether a Configurator release's supported version is the right fit.

Should I use Clover Configurator or OpenCore Configurator for my hackintosh build?

Choose based on your bootloader, not on which tool looks newer: Clover Configurator is for Clover-based systems, and OpenCore Configurator is for OpenCore-based systems. For a new build, OpenCore is the usual starting point, so OpenCore Configurator is the matching choice; if you are maintaining an existing Clover setup, use Clover Configurator.

How they differ in practice

Situation Better fit Why
New hackintosh build OpenCore Configurator OpenCore is the actively developed bootloader, and the tool tracks its releases closely
Existing Clover installation Clover Configurator It edits Clover's config structure and quirks directly
Updating after a macOS point release Whichever matches your bootloader Clover Configurator had a fix for macOS 15.4 compatibility, showing that OS updates can break older setups
Managing bootloader version changes OpenCore Configurator Its changelog entries regularly add support for new OpenCore versions

On mackie100 projects, the changelogs show this split clearly. OpenCore Configurator releases are mostly "OpenCore X.Y.Z supported" updates, such as version 2.78.2.0 adding OpenCore 1.0.8 support. Clover Configurator releases add or adjust specific config keys, such as ClearTaskSwitchBit, DisableIoMapperMapping and ResizeGpuBars in version 5.29.0.0. That pattern tells you something useful: the OpenCore tool is mainly a compatibility layer for a moving bootloader, while the Clover tool is more about granular config editing for a mature one.

A practical next step

Check which bootloader your EFI partition actually uses before downloading anything. If you see an OC folder with an OpenCore.efi file, use OpenCore Configurator; if you see Clover's structure, use Clover Configurator. Then match the configurator version to your bootloader version using the changelog, since a mismatch can produce confusing config errors. Keep a backup of your config file before editing, and treat any configurator as a convenience over hand-editing—it does not validate whether a quirk is correct for your hardware.

Why did Clover Configurator 5.28.0.1 fix a bug specifically for macOS 15.4?

Clover Configurator 5.28.0.1 was released on April 12, 2025 with a single listed change: "Fixed critical bug in macOS 15.4." The changelog on mackie100 projects does not state what the bug was or why it appeared in that particular macOS update—it only records that the fix was tied to 15.4 and describes it as critical.

What can reasonably be inferred

  • The trigger was the OS update, not a new app feature. No new settings, keys or OpenCore/Clover version support were announced alongside it, unlike the neighbouring entries (such as 5.29.0.0 adding ClearTaskSwitchBit, DisableIoMapperMapping and ResizeGpuBars keys). That points to a compatibility repair rather than added functionality.
  • "Critical" suggests the app was unusable or unsafe to rely on under 15.4. For a config editor, plausible failure modes are crashes on launch, failure to open or save a config.plist, or corrupted output—serious for anyone mid-build.
  • A point release (5.28.0.1) signals urgency. It was issued quickly after the OS change rather than bundled into a scheduled minor version.

Practical takeaway

If you are on macOS 15.4 or later, use 5.28.0.1 or newer before editing any Clover configuration; earlier 5.28 builds may misbehave. Before saving, keep a backup copy of your config.plist and verify the file still parses after an edit. If you also maintain an OpenCore setup, check that your Configurator version matches your bootloader release—the same changelog shows OpenCore Configurator 2.78.2.0 tracking OpenCore 1.0.8.

Where can I download the latest OpenCore Configurator update?

The latest OpenCore Configurator update listed is version 2.78.2.0, released April 20, 2026, which adds support for OpenCore 1.0.8. The changelog post on mackie100 projects includes a "Download here" link in that entry, so that page is the place to get the current build.

Practical notes

  • Match versions to your OpenCore release. Each Configurator update tracks a specific OpenCore version (2.78.1.0 for OpenCore 1.0.6, 2.78.0.2 for 1.0.5). If you're still on an older OpenCore, updating the Configurator alone won't upgrade your bootloader — you need the matching OpenCore files too.
  • Keep a backup of your working config. Before applying changes with a new Configurator build, save a copy of your config.plist so you can roll back if a newer version behaves unexpectedly.
  • Check the changelog first. The site lists entries by version and date, which helps you confirm whether a fix you need (for example, compatibility with a recent macOS release) is included.

As a next step, open the version 2.78.2.0 changelog entry, confirm your OpenCore version, then download and compare the new build against your existing setup before editing anything critical.

Related questions

More questions →
What the New Quirks Keys in mackie100 projects Changelogs Refer To

The three keys added in Clover Configurator 5.29.0.0 — ClearTaskSwitchBit, DisableIoMapperMapping, and ResizeGpuBars — are advanced boot-configuration options that sit in the Quirks section of a Clover setup. Each belongs to a different Quirks category: Booter, Kernel, and UEFI respectively. They are low-level switches that change how the bootloader hands hardware and memory behavior to macOS, and they only matter if you are building or maintaining a Hackintosh-style boot configuration. The changelog lists the keys and their locations but does not explain what they do, so the practical meaning has to come from the corresponding bootloader documentation.

Where the keys sit in the configuration

Quirks are grouped by the boot stage they affect, and the changelog places each new key in one of those groups:

Key Quirks category Stage affected
ClearTaskSwitchBit Booter Early boot / firmware handoff
DisableIoMapperMapping Kernel Kernel and memory mapping
ResizeGpuBars UEFI UEFI firmware and PCIe device setup

This grouping is the main clue to what each key touches. A Booter quirk changes behavior before the kernel takes over; a Kernel quirk changes how the kernel sees memory or devices; a UEFI quirk changes what the firmware exposes to the OS.

Booter: ClearTaskSwitchBit

A Booter-stage quirk affects the transition from firmware to the macOS kernel. The name refers to a task-switch control bit, which is a CPU/firmware-level flag rather than a user-facing macOS setting. In practice, keys like this exist to work around firmware or CPU behavior that would otherwise interfere with booting. Treat it as a compatibility switch: you enable it only when a specific boot problem points to it, not as a default.

Kernel: DisableIoMapperMapping

This key sits in the Kernel Quirks group, which governs how the kernel maps memory and devices. The name points to I/O mapper mapping — the translation layer between devices and memory. Disabling that mapping is the kind of change made to avoid conflicts on certain hardware, and it can carry side effects for device access. It is an advanced option, not something to toggle without a documented reason.

UEFI: ResizeGpuBars

This is a UEFI-stage quirk, so it changes what the firmware presents to the OS before macOS starts. "GPU BARs" refers to Base Address Registers — the memory windows a PCIe device such as a graphics card exposes. Resizing them changes how much address space the GPU is given. This is relevant when a GPU's default BAR sizing causes problems, and it depends on both the firmware and the card supporting the change.

How to use these entries

The changelog is a release note, not a manual. To act on it:

  1. Confirm you are on Clover Configurator 5.29.0.0 or later, since earlier versions will not show these keys.
  2. Open the Quirks section and locate the matching category (Booter, Kernel, or UEFI).
  3. Read the bootloader's own documentation for that key before changing it — the changelog gives the name and location only.
  4. Change one key at a time and verify boot behavior after each change, so you can tell which switch caused an effect.

The expected result of a correct change is that a specific boot or hardware issue disappears; if nothing changes, the key was probably not the cause and should be reverted.

What the changelog does and does not tell you

The page evidence confirms the version, date (April 21, 2026), the three key names, and their Quirks categories. It does not describe the effect of each key, the hardware it targets, or recommended values. Those details belong to the bootloader documentation the keys originate from, and the site's own framing — Clover, OpenCore, bootloader, UEFI, Hackintosh — shows these are customization tools for advanced users rather than general macOS settings.

A useful way to read the entry: it is a signal that the configurator now exposes three more advanced switches, grouped by boot stage. Whether you need any of them depends on a concrete problem you are troubleshooting, not on the fact that they were added.

What Is mackie100 projects?

mackie100 projects (mackie100projects.altervista.org) is the release and changelog site for two macOS boot-configuration utilities: Clover Configurator and OpenCore Configurator. It is relevant to you if you build or maintain a Hackintosh (macOS on non-Apple hardware) and need to edit Clover or OpenCore bootloader settings, UEFI quirks, or themes. The site itself is not a tutorial resource — it publishes version notes and "Download here" links for each release.

What the site actually publishes

The homepage is a running feed of changelog posts, each tied to one product version. Posts follow a consistent pattern: product name, version number, release date, a short list of changes, and a download link.

Product Latest version shown Date Notable change
Clover Configurator 5.29.0.0 Apr 21, 2026 Added ClearTaskSwitchBit (Quirks → Booter), DisableIoMapperMapping (Quirks → Kernel), ResizeGpuBars (Quirks → UEFI)
OpenCore Configurator 2.78.2.0 Apr 20, 2026 OpenCore 1.0.8 supported
OpenCore Configurator 2.78.1.0 Aug 29, 2025 OpenCore 1.0.6 supported
Clover Configurator 5.28.0.1 Apr 12, 2025 Fixed critical bug in macOS 15.4
OpenCore Configurator 2.78.0.2 Apr 12, 2025 OpenCore 1.0.5 supported

Two things stand out from this pattern. First, OpenCore Configurator releases are primarily driven by upstream OpenCore versions — a new entry usually means "this build of the configurator can open and edit configs for OpenCore X." Second, Clover Configurator updates are more often feature- or bug-driven, such as the macOS 15.4 fix in 5.28.0.1.

Which tool applies to your setup

The choice is not a preference — it follows from which bootloader your machine already uses.

  • OpenCore Configurator — for systems booting via OpenCore. Match the configurator version to your OpenCore release; the changelog tells you which OpenCore version each build supports. If you are on OpenCore 1.0.8, the 2.78.2.0 entry is the one that names it.
  • Clover Configurator — for systems still booting via Clover. The 5.29.0.0 entry shows the kind of edits it covers: booter, kernel, and UEFI quirk keys exposed as editable fields rather than raw plist text.

If you are starting fresh, note that the site does not argue for one bootloader over the other; it only ships editors for both. Your decision should come from your bootloader choice, not from this site.

How to use a changelog post

Each post is short, so the workflow is quick:

  1. Identify your current bootloader version (OpenCore or Clover) from your existing config or boot picker.
  2. Scan the feed for the matching product and find the newest entry that names your version or a compatible one.
  3. Read the change list before downloading. For Clover 5.29.0.0, for example, the three added keys are new editable properties — if your config does not use them, the update mainly gives you the fields for future edits.
  4. Use the "Download here" link in that post. The site does not host a separate downloads page in the material shown; the link lives inside each changelog entry.

Common sticking points

  • Version mismatch is the usual failure. Opening an OpenCore 1.0.8 config in a configurator built for 1.0.6 can leave newer keys unrepresented. Check the "supported" line in the changelog before editing.
  • A bug-fix release is not optional if you are on the affected OS. The 5.28.0.1 note ("Fixed critical bug in macOS 15.4") is the clearest example — if you run that macOS version with Clover, that update is the one to take.
  • The site gives no setup instructions. It assumes you already know where your config.plist lives and what the quirk keys do. For the meaning of entries like ResizeGpuBars, you need the upstream OpenCore or Clover documentation, not this feed.

Practical takeaway

Treat mackie100 projects as a version-tracking and download source, not a guide. Bookmark it if you maintain a Hackintosh and want to know when a configurator build catches up to a new OpenCore release or patches a macOS compatibility bug. The site lists PayPal among its payment platforms, but the changelog posts shown do not state pricing or whether downloads require payment — check the individual post and link before assuming either way.

How to Check Which OpenCore or macOS Version an OpenCore Configurator Release Supports

Open the OpenCore Configurator changelog entry for the release you are considering and read the "What's New" line directly under the version number. On mackie100 projects, each OpenCore Configurator changelog post states the supported OpenCore version in that line (for example, "OpenCore 1.0.8 supported"), and the post date tells you how current that support is. macOS compatibility is only mentioned when a release fixes a specific macOS bug, so treat the OpenCore version as the primary compatibility signal and the macOS note as an additional, occasional one.

Where the information lives

The site publishes one changelog post per release, filed under "OpenCore Configurator Changelog." Each post follows the same pattern:

  • A title with the version number, e.g. "OpenCore Configurator Changelog version 2.78.2.0"
  • A "What's New in Version X" line with the release date
  • A short bullet or sentence naming the supported OpenCore version
  • A "Download here" link

Because the supported OpenCore version is written in the body text rather than a separate compatibility table, you read it from the post itself, not from a spec sheet.

Reading the version mapping

The changelog entries on the site show this pattern:

OpenCore Configurator version Post date Stated support
2.78.2.0 Apr 20, 2026 OpenCore 1.0.8 supported
2.78.1.0 Aug 29, 2025 OpenCore 1.0.6 supported
2.78.0.2 Apr 12, 2025 OpenCore 1.0.5 supported
2.78.0.0 Mar 9, 2025 OpenCore 1.0.5 supported
2.77.1.0 Nov 20, 2024 OpenCore 1.0.3 supported
2.77.0.0 Oct 15, 2024 OpenCore 1.0.3 supported

Two things follow from this. First, the Configurator version number and the OpenCore version number move independently — a small jump in the Configurator version can still mean a new OpenCore target. Second, the same OpenCore version can appear in more than one Configurator release (1.0.5 appears in both 2.78.0.0 and 2.78.0.2), so the newest Configurator is not automatically required for a given OpenCore build.

Matching a release to your setup

  1. Note the OpenCore version you are running or plan to install.
  2. Scan the changelog list for the newest post whose "What's New" line names that version or a later one.
  3. Check the post date. If the entry is old relative to your OpenCore build, a newer Configurator release likely exists further up the changelog.
  4. Open that post and use its "Download here" link to get the matching build.

If your OpenCore version does not appear in any entry, the site's changelog does not document support for it — do not assume compatibility from a nearby version number.

What about macOS compatibility?

macOS mentions are rarer and narrower than OpenCore mentions. In the entries shown, the only macOS-specific note is Clover Configurator 5.28.0.1 (Apr 12, 2025), described as fixing "critical bug in macOS 15.4." That is a Clover tool, not OpenCore Configurator, and it describes a bug fix rather than a supported macOS range. For OpenCore Configurator, the changelog does not list macOS version requirements, so you cannot confirm macOS compatibility from these posts alone — the OpenCore version line is the only compatibility statement the site provides.

Practical cautions

  • The changelog is a release log, not a compatibility matrix. Absence of a macOS note does not mean a release is incompatible with your macOS version; it means the site did not state anything about it.
  • Dates matter. An entry naming your OpenCore version but published many months ago may have been superseded; check whether a later post names a newer OpenCore version before settling on the older download.
  • The site lists PayPal among its payment signals, but the changelog posts themselves present downloads through "Download here" links without stated pricing or login requirements in the excerpt — verify on the actual post page before assuming access terms.
Where to Download Clover Configurator or OpenCore Configurator from mackie100 projects

Download links are inside each version's changelog post on mackie100 projects. Open the changelog entry for the version you want, confirm its version number and release date, then use the "Download here" link in that post. The site's visible changelog listings do not state extra download conditions, account requirements, or pricing.

How the download pages are organized

The site publishes separate changelog posts for two tools:

Tool What the changelog shows Example entries
Clover Configurator Version number, release date, list of added or fixed items 5.29.0.0 (Apr 21, 2026); 5.28.0.1 (Apr 12, 2025)
OpenCore Configurator Version number, release date, which OpenCore release is supported 2.78.2.0 (Apr 20, 2026, OpenCore 1.0.8); 2.78.1.0 (Aug 29, 2025, OpenCore 1.0.6)

Each post follows the same pattern: a title with the tool name and version, a "What's New" section, and a "Download here" link at the end.

Steps to get the right file

  1. Decide which tool you need: Clover Configurator for Clover-based setups, OpenCore Configurator for OpenCore-based setups.
  2. Find the newest changelog post for that tool. For OpenCore Configurator, check that the supported OpenCore version matches the OpenCore release you are configuring.
  3. Read the "What's New" list to confirm the version fixes or adds what you need. For example, Clover Configurator 5.28.0.1 notes a fix for a critical bug in macOS 15.4.
  4. Click "Download here" in that post.
  5. Verify what you received: the file should correspond to the version named in the post title, and the post date should match the changelog date.

Common sticking points

  • Mixing up tools: Clover and OpenCore changelogs are separate post categories. A Clover Configurator download will not configure an OpenCore EFI, and the reverse is also true.
  • Version mismatch: OpenCore Configurator posts name the OpenCore version they support (for example, 2.78.2.0 supports OpenCore 1.0.8). If your OpenCore release is newer or older, check whether a different changelog entry covers it before downloading.
  • Old posts: Older entries remain listed, so the first download link you see may not be the latest. Sort by the post date in the title area rather than by position on the page.
  • No stated requirements: The changelog pages in the available site content do not describe system requirements or install steps beyond the download link, so treat the changelog notes as the main compatibility signal.
What Are Clover Configurator and OpenCore Configurator on mackie100 projects?

mackie100 projects is a small software site that publishes two macOS configuration utilities for Hackintosh bootloaders: Clover Configurator for the Clover bootloader and OpenCore Configurator for the OpenCore bootloader. Both tools let you edit the bootloader's configuration file through a graphical interface instead of hand-editing plist files. The site's main public content is the changelog and download link for each release, so it works best as a version-tracking and download source rather than a full documentation hub.

What each tool is for

Tool Works with Typical job
Clover Configurator Clover bootloader Edit Clover's config, including Quirks and boot settings
OpenCore Configurator OpenCore bootloader Edit OpenCore's config.plist, including kernel, booter, and UEFI quirks

The split matters: a config file for one bootloader is not interchangeable with the other. If your machine boots through OpenCore, you want OpenCore Configurator; if it boots through Clover, you want Clover Configurator.

How the site is organized

Releases are posted as dated changelog entries, each with a "Download here" link. Recent entries from the site show the pattern:

  • Clover Configurator 5.29.0.0 (Apr 21, 2026) — added ClearTaskSwitchBit under Quirks → Booter, DisableIoMapperMapping under Quirks → Kernel, and ResizeGpuBars under Quirks → UEFI.
  • OpenCore Configurator 2.78.2.0 (Apr 20, 2026) — added support for OpenCore 1.0.8.
  • OpenCore Configurator 2.78.1.0 (Aug 29, 2025) — added support for OpenCore 1.0.6.
  • Clover Configurator 5.28.0.1 (Apr 12, 2025) — fixed a critical bug on macOS 15.4.
  • OpenCore Configurator 2.78.0.2 (Apr 12, 2025) — added support for OpenCore 1.0.5.

Two things follow from this. First, OpenCore Configurator versions are tied to specific OpenCore releases, so match the tool version to the OpenCore version you actually run. Second, Clover Configurator changes are often macOS-version fixes, which is why the 5.28.0.1 note about macOS 15.4 is worth heeding if you are on that OS.

How to use it

  1. Identify your bootloader (Clover or OpenCore) and, for OpenCore, your exact OpenCore version.
  2. Open the matching changelog entry on mackie100 projects and confirm the version supports your setup.
  3. Use the "Download here" link in that entry.
  4. Before editing, back up your existing config file so you can restore it if a change breaks booting.

The site lists PayPal among its payment platforms, but the changelog pages themselves do not state pricing or login requirements for downloads, so check the download page itself rather than assuming free access.

Common pitfalls

  • Version mismatch. An OpenCore Configurator build made for OpenCore 1.0.8 may expose keys your older OpenCore does not recognize. Match versions first.
  • Editing the wrong file. Clover and OpenCore configs are different formats; opening one in the other tool will not produce a working result.
  • Skipping the backup. A single wrong quirk can stop the machine from booting, and recovery means editing the config from another system or a recovery environment.

If you only need to know what the site is: it is the release home for these two configurators, with dated changelogs and per-version download links.

Website Overview

Identifiable technologies and additional version or configuration signals make the service easier to fingerprint, which may help targeted scanners narrow their checks. An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality.

Domain and Registration

Registered in 2000, this domain has about 25 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is Tucows Domains Inc., a widely used domain service provider. The domain uses the common .org extension, which is not an independent safety signal.

DNS and Email

The observed email authentication setup is incomplete: DMARC is missing. Nameservers are provided by altervista.org, indicating managed DNS hosting. MX records point to the altervista.org email service. TXT records include verification markers for Google. Such markers may also remain after a service stops being used. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Amazon cloud or CDN ecosystem. The certificate is valid for about 394 days in total, with 57 days remaining.

HTTP and Browser Security

The response lacks these common security headers: HSTS, X-Content-Type-Options, Referrer-Policy, clickjacking protection. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The via response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers. The Server header identifies Apache without an exact version.

Technology Stack Analysis

The public page identifies WordPress 7.0.3, jQuery, Apache, with exact versions exposed for 1 technologies. These details can narrow vulnerability checks, although exposure alone is not a vulnerability.

Search and Social Sharing

The Generator tag identifies WordPress 7.0.3, making the publishing system easier to fingerprint. Twitter Card metadata is configured. JSON-LD includes Organization data, helping describe the organization as an entity. The title has 18 characters, within a common display range. A meta description is present, with 121 characters.

Hosting and Email

DNSaltervista.org
Hostingaltervista.org
Emailaltervista.org
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Germany flagFalkenstein, Saxony, Germany Inferred 138.201.201.18

Registration details

RDAP / WHOIS

RegistrarTucows Domains Inc.
Registered2000-12-22
Expires2034-12-22
Domain statusclient transfer prohibited、client update prohibited
Nameserversns1.altervista.org、ns2.altervista.org、ns3.altervista.org、ns4.altervista.org
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Ahzpxvn.a2.altervista.org138.201.201.18300—
Ahzpxvn.a2.altervista.org176.9.79.149300—
Ahzpxvn.a2.altervista.org195.201.193.180300—
Ahzpxvn.a2.altervista.org213.133.97.172300—
Ahzpxvn.a2.altervista.org88.99.101.219300—
Ahzpxvn.a2.altervista.org88.99.2.209300—
Ahzpxvn.a2.altervista.org88.99.2.210300—
Ahzpxvn.a2.altervista.org88.99.2.212300—
Ahzpxvn.a2.altervista.org88.99.2.213300—
Ahzpxvn.a2.altervista.org94.130.164.5300—
Ahzpxvn.a2.altervista.org94.130.206.224300—
MXaltervista.orgmail.altervista.org8640010
MXaltervista.orgmail2.altervista.org8640020
NSaltervista.orgns1.altervista.org86400—
NSaltervista.orgns2.altervista.org86400—
NSaltervista.orgns3.altervista.org86400—
NSaltervista.orgns4.altervista.org86400—
TXTaltervista.orggoogle-site-verification=IgCFbXFHbsQ_WiLNZYx6Lroo28PHjohwpYm1tNBe8l87200—
TXTaltervista.orggoogle-site-verification=Y3EBg_m4sI-TTf0xEiBKIGuoLXFcARP1ayikGMIy4O47200—
TXTaltervista.orgv=spf1 redirect=_spf.ml.altervista.org7200—
CNAMEmackie100projects.altervista.orghzpxvn.a2.altervista.org600—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectaltervista.org
IssuerAmazon
Valid until2026-12-18T23:59 · Remaining when checked: 57 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=UTF-8
serverApache
content-security-policyupgrade-insecure-requests
permissions-policyprivate-state-token-redemption=(self "https://www.google.com" "https://www.gstatic.com" "https://recaptcha.net" "https://challenges.cloudflare.com" "https://hcaptcha.com"), private-state-token-issuance=(self "https://www.google.com" "https://www.gstatic.com" "https://recaptcha.net" "https://challenges.cloudflare.com" "https://hcaptcha.com")

Identified technologies

WordPress 7.0.3jQueryApache

Pages, Search and Sharing

Meta descriptionclover, bootloader, opencore, bios, custom, hackintosh, mac, osx, personalize, bootsoftware, themes, uefi, windows, games
Canonical URLhttps://mackie100projects.altervista.org/
LanguageEnglish (default)
Twitter Cardsummary_large_image
All bots 2 allowed · 1 disallowed
  • Allow/wp-admin/admin-ajax.php
  • Allow/ads.txt
  • Disallow/wp-admin/

User reviews (0)

  • No reviews yet.