Website profiles · Technology insights · Alternatives

musicbrainz.org No paid content found

Categories: Social & Community

Visit website

Updated: 2026-09-23 17:22 Language: English (default) Access: Normal

Profile views 0 Outbound visits 0
MusicBrainz Full homepage screenshot
Editorial Review

Website Review

What is MusicBrainz?

MusicBrainz is an open music encyclopedia: a community-built database of music metadata — artists, releases, recordings, works, labels, and the relationships between them — published under open licenses so anyone can reuse it. It is run by the MetaBrainz Foundation, a non-profit, and anyone can create an account and contribute edits, similar to how Wikipedia works.

What it actually contains

Rather than storing audio, it stores structured facts about music:

  • Entities: artists, release groups, releases, recordings, works, series, labels, places, areas, instruments, and events.
  • Relationships: links such as "member of band," "performer on recording," "cover of," or "released by label."
  • Identifiers: stable IDs that let software match the same song or album across different services.
  • Tags and genres: community-applied labels for browsing and filtering.

Who it is for

  • Listeners and collectors who want clean, consistent artist and release information.
  • Software developers who need a free API and data feed to power players, taggers, or catalogues.
  • Librarians and archivists describing recorded music in a structured way.
  • Contributors who enjoy editing and cross-checking metadata as a hobby.

How people use it in practice

A common entry point is MusicBrainz Picard, the official tagger: it reads the acoustic fingerprint or existing tags of your files, looks them up in the database, and writes back consistent artist, album, and track names. Other taggers listed on the site include AudioRanger, Mp3tag, and Yate Music Tagger. Beyond tagging, the database is queried through the MusicBrainz API and a live data feed, so a developer can resolve "which recording is this?" without maintaining their own catalogue.

If you are deciding whether to rely on it, check three things: whether the releases you care about are already well-populated, whether the open data license suits your project, and whether you need the API or just the tagger. Start by searching for a few albums you know well — if their entries look complete and correctly linked, the data will likely serve you; if not, you can either fix them yourself or treat coverage as a caveat. Related projects worth knowing are MetaBrainz Foundation for the organisation behind it and AcoustID for the fingerprinting that makes automatic matching possible.

How do I get started contributing to MusicBrainz?

Start by creating a free account, then use the Beginners guide and Editing introduction to learn how the data model works before you touch a real release. MusicBrainz is community-maintained, so the fastest path is to fix small, verifiable things first rather than attempt a large artist or discography import on day one.

A practical first session

  1. Create an account and read the Beginners guide and Editing introduction from the Documentation section.
  2. Add one release you own, using the barcode and catalog number from the physical copy or your files.
  3. Run that release through MusicBrainz Picard to see how the database identifies recordings and release groups.
  4. Check the Style guidelines for the specific artist type you're editing — classical, soundtrack and various-artists releases have their own conventions.
  5. Ask in the forums or bug tracker if an edit gets voted down; the reason is usually a style rule, not a mistake in your data.

What each entry point is for

Starting point Best for Trade-off
Beginners guide Learning terminology (artist, release, release group, recording) Read-only; you still have to make the edit yourself
Picard Matching your own library and spotting missing releases Requires files with decent tags to be useful
Forums / bug tracker Resolving disputes and reporting data problems Slower than just editing, but prevents repeat errors

Whose experience this reflects

The page itself doesn't contain contributor reviews, so the following is general advice rather than a logged experience: newcomers typically find the release-group versus release distinction the first real hurdle. A concrete reader scenario — you own a 2015 remaster with bonus tracks — means you'd add the release, then link it to the existing release group rather than creating a duplicate one.

Deciding where to spend your time

If you want low-friction wins, tag your own music and fill in missing CD stubs. If you want to shape the data long-term, learn the style guidelines for one genre and become a reliable voter on edits in that area. The MusicBrainz Database and API pages are worth a look later if you'd rather work programmatically than through the web editor.

For background on the organisation behind the project, see MetaBrainz Foundation.

Which music tagging apps like Picard work with MusicBrainz?

MusicBrainz lists several tagging tools that use its database, but they are not interchangeable: they differ in how much they automate, which platforms they run on, and how deeply they integrate with MusicBrainz identifiers.

Tools named by MusicBrainz

  • MusicBrainz Picard — the project's own cross-platform tagger, built around acoustic fingerprinting and MusicBrainz release matching.
  • AudioRanger — a tagger aimed at tidying whole libraries, listed among the MusicBrainz-compatible products.
  • Mp3tag — a long-established tag editor with broad format support, also listed as a MusicBrainz-aware product.
  • Yate Music Tagger — a macOS-focused tagger in the same list.

Mobile and server-side options

  • MusicBrainz for Android — an Android app for looking up and contributing MusicBrainz data.
  • MusicBrainz Server — the software behind the site, self-hostable for anyone wanting their own instance.
  • MusicBrainz Database — the downloadable dataset itself, which other taggers can query.

How to choose If you want the reference implementation and the tightest match to MusicBrainz releases, start with Picard. If you work mainly on macOS, Yate is the natural alternative. If you prefer a general-purpose Windows editor and only occasionally need MusicBrainz lookups, Mp3tag fits that pattern. AudioRanger suits people who want automated cleanup across a large collection rather than manual editing.

A practical next step: pick one album you know well, tag it with two of these tools, and compare how each handles multi-artist releases and compilation flags — that difference usually decides which tool you keep. For background on the underlying data, see MusicBrainz.

How can I use the MusicBrainz API in my own project?

Use the MusicBrainz API when your project needs stable identifiers and structured metadata for artists, releases, recordings, works and relationships — for example, to look up a release by barcode, resolve messy artist names to canonical IDs, or enrich a library with credits and release dates. It is a read-oriented web service; you query it with HTTP and get JSON or XML back. The official starting point is MusicBrainz, which links to the API, the live data feed, and the database itself.

Typical integration paths

  • On-demand lookups. For a player, catalogue or tagging tool, call the API when a user opens an item or scans a file. This keeps local storage small but makes you dependent on network latency and rate limits.
  • Bulk or offline work. For analytics or a large library, the downloadable database and live data feed suit repeated, high-volume processing better than hammering the query endpoint.
  • Client libraries. Community libraries exist for many languages; they mostly wrap the same endpoints and handle parsing for you. Treat them as convenience, not a different data source.

Practical rules

  • Set a descriptive User-Agent identifying your app and a contact URL or email. Anonymous or generic agents are the quickest way to get throttled.
  • Respect rate limiting: roughly one request per second per client is the commonly cited ceiling, and it is enforced. Queue requests and cache responses rather than firing parallel bursts.
  • Use MusicBrainz IDs (MBIDs) as your primary keys and store them alongside your own IDs. Names are ambiguous and change; MBIDs do not.
  • Handle missing data as normal. Coverage is community-driven, so a release may exist with no cover art, incomplete credits or no linked relationships.
  • Data is under open licences, but some derived content (notably cover art) has separate terms. Check the licence pages before redistributing.

Choosing between API and data dump

Need Better fit
Occasional lookups while a user waits API
Millions of records, repeatable processing Database dump / live feed
Always-current single record API
Full local search index Dump plus your own search engine

A concrete first step

Pick one narrow task, such as resolving an artist name to an MBID, and build that single call with caching and a proper User-Agent before expanding. If you need a working example of a client that does this well, look at the tools listed on the site, such as MusicBrainz Picard, and read their source.

What are MusicBrainz's data licenses and how can I reuse the data?

MusicBrainz publishes its core data under open licenses and separates that data from the software used to run and edit the database. The practical split matters: you can reuse the metadata for many purposes, but the server code and some supplementary content carry different terms.

What is licensed how

Material Typical license What it means for reuse
Core music metadata (artists, recordings, releases, works, etc.) Public domain / CC0-style dedication You can copy, modify, redistribute and even use it commercially without asking permission.
Live Data Feed and database dumps Same open terms as the core data, with format and access conditions set by MusicBrainz You can build mirrors, apps and research datasets, but you must handle the feed format and keep attribution/versioning clear.
MusicBrainz Server software Open-source license (GPL-family) You can self-host and modify the code, but derivative distributions must follow the code license.
Cover art, annotations and some user-contributed extras May be under separate terms Check the individual item; not everything on the site is automatically CC0.

The exact license text and current terms are linked from the site's data licenses page. Treat that page as authoritative rather than any summary, including this one.

How to reuse the data in practice

  • For an app or website: use the MusicBrainz API for lookups and the Live Data Feed or database dumps for bulk work. The API is rate-limited, so cache responses and identify your client with a meaningful user agent.
  • For research or archiving: download the regular database dumps. They are the most complete and stable option, and they avoid hammering the live API.
  • For tagging your own files: the MusicBrainz Picard tagger is the intended client. It matches your files against the database and writes identifiers and metadata back to the files.
  • For commercial products: the core data's public-domain-style dedication generally permits commercial use, but you still need to comply with any separate terms on artwork or user-contributed content, and with the code license if you redistribute the server.

Trade-offs to weigh

The open license is the main advantage: no per-record fees, no lock-in, and a stable identifier system that lets different services talk about the same recording. The trade-off is that the data is community-maintained. Coverage of mainstream releases is strong, but niche, regional or very new material may be incomplete or inconsistently styled. Bulk dumps are large and require real storage and processing capacity; the live API is easier but rate-limited and unsuitable for full-database operations.

If you are deciding between sources, a concrete test is to pick ten recordings you care about and check how completely each source identifies them — including release, track and artist relationships. MusicBrainz tends to win on identifier stability and open reuse; commercial databases often win on editorial polish and coverage of obscure catalogs. Related open-metadata projects worth knowing are Discogs for a large community-maintained commercial catalog and Wikidata for linked identifiers across many domains.

How does MusicBrainz identify music so that people and machines can talk about it unambiguously?

MusicBrainz identifies music by assigning stable, shared identifiers to entities and by modelling the relationships between them, so a track, release or artist is not just a string of text that different people spell differently.

How identification works in practice

  • Entities are typed and named separately: artists, release groups, releases, recordings, works, labels, places, areas and series each have their own entry.
  • Each entity has a MusicBrainz ID (MBID), a permanent identifier that stays the same even if a name is corrected, translated or re-styled.
  • Releases are linked to release groups, recordings to works, and artists to releases through relationships, so one song can be traced across many albums and versions.
  • Recordings are distinguished from releases: the same recording can appear on multiple releases, which is how compilations and reissues are handled without duplicating the underlying audio identity.
  • Disambiguation comments and aliases handle artists or releases with the same name, so two different "Doves" do not collapse into one entry.

Why this matters for machines

Because the identifiers are stable and exposed through an API and a live data feed, software can match a local file to the right entity instead of guessing from a filename. A tagger can look up an MBID and write consistent metadata back to your files, and a player or library can group your copies of the same recording even when the album titles differ.

Why this matters for people

For a listener or collector, the payoff is that a scrobble, a playlist entry or a CD rip can point to the same thing everyone else means. A concrete scenario: you rip a compilation and a studio album that both contain the same song. With MBIDs, your library can recognise them as the same recording while still showing the two different releases — something a plain artist-and-title tag cannot do.

Trade-offs to know

The model is precise but demanding. Adding a release properly means matching it to an existing release group, choosing the right recordings, and following style guidelines; a quick CD stub is easier but less complete. Coverage depends on contributors, so obscure or newly released material may be thin until someone edits it. The open licence also means anyone can reuse the data, which is the point, but it puts the burden of accuracy on community review rather than a single authority.

A useful next step

If you want to see the identification in action, install a tagger that reads MBIDs — MusicBrainz Picard is the project's own tool — and use "lookup" or "scan" on a few files with messy tags. Compare the result against MusicBrainz itself: search for the release, check whether the recordings match, and note where your files disagreed. That gap is usually where ambiguous naming was costing you.

Related questions

More questions →
Who operates MusicBrainz?

MusicBrainz is operated by the MetaBrainz Foundation, a California-based 501(c)(3) tax-exempt non-profit corporation. The Foundation describes its mission as keeping MusicBrainz free and open source.

What the operator relationship means

MusicBrainz is an open music encyclopedia that collects music metadata and makes it available to the public. It is maintained by a global community of users, in a way comparable to Wikipedia, and anyone can participate and contribute. The MetaBrainz Foundation handles the organizational side — the legal and financial entity behind the project — while the data itself is contributed and curated by that community.

Two stated aims of the project follow from this setup:

  • Open data: MusicBrainz releases its data under open licenses, so it can be reused rather than locked behind the operator.
  • Unambiguous music identification: It provides a reliable, unambiguous form of music identification intended to work for both people and machines.

Where to verify the details

The site's About us section is the canonical place for organizational information, alongside pages for sponsors, the team, and the shop. Related policy pages — data licenses, social contract, code of conduct, privacy policy, GDPR compliance, and copyright/DMCA compliance — sit in the same footer area and describe how the non-profit operates the service.

If your question is about using MusicBrainz rather than who runs it, the same site organizes material into a few practical entry points:

Need Where to start
Tagging your music MusicBrainz Picard, AudioRanger, Mp3tag, Yate Music Tagger
Learning to edit Beginners guide, Editing introduction, Style guidelines, FAQs
Contributing How to contribute, Bug tracker, Forums
Building on the data MusicBrainz API, Live Data Feed, MusicBrainz Database, Developer resources

One thing to keep in mind

"Operated by a non-profit" tells you about governance and licensing intent, not about cost or account requirements for any particular tool or service. The site lists no pricing signals in the material available here, so don't assume free access or no login for every product — check the specific product or documentation page for those conditions.

How to Contribute to MusicBrainz

Anyone can contribute to MusicBrainz by creating a free account and editing the music metadata in its open database. The site is maintained by a global community of users, and its own documentation states that it wants "everyone — including you — to participate and contribute." You do not need special credentials to start; you begin as a regular editor and can take on more responsibility over time.

What you are actually contributing

MusicBrainz is an open music encyclopedia that collects music metadata and releases it under open licenses. Its data model is built around entities you will edit repeatedly:

Entity What it represents
Artist A person or group
Release A specific published edition (e.g., a CD pressing)
Release group The abstract album/single that releases belong to
Recording A single audio recording
Work The underlying composition
Label, Place, Event, Series, Area, Instrument Supporting entities

Contributions are edits to these entities: adding a missing release, fixing a misspelled artist name, linking a recording to its work, adding a label, and so on.

Steps to start contributing

  1. Create an account. Use the "Create account" link on the site. Logging in is what lets you make edits rather than just browse.
  2. Read the Beginners guide. MusicBrainz provides a dedicated Beginners guide as the entry point for new editors.
  3. Read the Editing introduction. This explains how the editing system works before you touch real data.
  4. Learn the Style guidelines. These exist so that data stays consistent across a global community of editors. Following them is what makes your edits acceptable rather than reverted.
  5. Make your first edit. A common starting task is adding an artist or adding a release, both of which have dedicated how-to pages ("How to add artists," "How to add releases").
  6. Use the Community section. It explains how to contribute and links to the bug tracker and forums, where you can ask questions and discuss edits.

Tools that help you contribute

MusicBrainz lists several tagging tools that read and write MusicBrainz data. These are useful because tagging your own files is often how people first notice missing or wrong data:

  • MusicBrainz Picard — the official tagger
  • AudioRanger
  • Mp3tag
  • Yate Music Tagger
  • MusicBrainz for Android

A practical loop: tag your library with one of these, find a release that is missing or mismatched, then add or correct it in the database.

Ways to contribute beyond editing

  • Vote on and review edits. Experienced editors participate in the peer-review process that decides whether edits are accepted.
  • Report problems through the bug tracker.
  • Discuss and ask in the forums.
  • Help translate the interface — the site offers multiple languages and a "Help translate" link.
  • Become a privileged user. MusicBrainz has privileged user accounts and auto-editor elections for editors who earn trust over time.

Common sticking points

  • Skipping the style guidelines. Edits that ignore them tend to get voted down or reverted, which is discouraging for new editors.
  • Confusing release with release group. A release group is the abstract album; a release is one specific edition of it. Adding the wrong one creates duplicates.
  • Not checking for existing entries first. Search before adding, or you will create duplicates that others have to merge.
  • Expecting instant acceptance. Edits go through a community review process, so results are not always immediate.

Who runs it

MusicBrainz is operated by the MetaBrainz Foundation, a California-based 501(c)(3) tax-exempt non-profit corporation dedicated to keeping MusicBrainz free and open source. The project is funded and supported rather than ad-driven, which is why the data is released under open licenses and why community contribution is central to how it grows.

What tools does MusicBrainz offer for tagging music?

MusicBrainz itself is an open music encyclopedia that collects music metadata, but it also points users to a set of tagging tools that use that metadata to identify and organize music files. The main one is MusicBrainz Picard, with AudioRanger, Mp3tag, and Yate Music Tagger listed alongside it, plus MusicBrainz for Android for mobile use. These tools are relevant if you want your local files to carry consistent, machine-readable metadata rather than whatever came bundled with a download.

The tagging tools MusicBrainz lists

MusicBrainz groups these under a "Products" section on its site. The distinction that matters is between tools the project develops itself and third-party taggers that support MusicBrainz metadata.

Tool Who makes it Platform signal from the site What it's for
MusicBrainz Picard MusicBrainz / MetaBrainz Desktop (listed as a MusicBrainz product) Tagging and identifying music files using MusicBrainz metadata
AudioRanger Third party Listed under MusicBrainz products Tagging/organizing music files
Mp3tag Third party Listed under MusicBrainz products Tag editing
Yate Music Tagger Third party Listed under MusicBrainz products Tag editing
MusicBrainz for Android MusicBrainz / MetaBrainz Android Mobile access to MusicBrainz

The site presents Picard as the flagship tagging application — it appears first in the product list and is also referenced in the blog (for example, "Picard 3 Release Candidate" posts). The other three are taggers that work with MusicBrainz data but are maintained outside the project.

Why use MusicBrainz-linked tools at all

The stated goal of MusicBrainz is to be "a reliable and unambiguous form of music identification," so that "both people and machines" can talk about music meaningfully. A tagger that pulls from MusicBrainz is trying to replace messy, inconsistent tags with identifiers tied to a shared database — artist, recording, release, and release group entries that other software can also recognize.

That matters most when you have a large library where the same track appears with different spellings, missing album names, or no consistent artist field. Matching files against MusicBrainz metadata gives you one canonical set of values instead of several conflicting ones.

How to get started

  1. Pick a tool. For desktop tagging tied directly to MusicBrainz, Picard is the default starting point. If you already use Mp3tag or Yate, those are listed as compatible options.
  2. Check the beginner material. MusicBrainz links a Beginners guide, an Editing introduction, and Style guidelines. The tagging workflow and the editing workflow are related but not identical — tagging changes your files, editing changes the database.
  3. Tag a small batch first. Run one album through your chosen tool and inspect the result before processing an entire library, so you can see how matches are applied.
  4. For mobile, MusicBrainz for Android is the listed option.

What to watch for

  • Tagging is not the same as contributing. Tools like Picard write metadata to your files; contributing means adding or correcting entries in the MusicBrainz database itself. The site keeps these as separate paths (Quick start vs. How to contribute).
  • Third-party tools are third-party. AudioRanger, Mp3tag, and Yate are listed by MusicBrainz but not developed by it, so their behavior and support come from their own maintainers.
  • The site flags browser support. MusicBrainz notes that unsupported browsers may not work correctly and recommends a recent Firefox, Safari, Edge, or Chrome-based browser, with a legacy browser mode as a fallback.

If your goal is simply to make local files consistent and identifiable, start with Picard and the Beginners guide. If you want to improve the underlying data those tools rely on, that's the separate contribution path.

What You Can Do with MusicBrainz Data

MusicBrainz data is released under open licenses, so you can reuse it for both human-facing and machine-facing purposes. The site describes itself as an open music encyclopedia that collects music metadata and makes it available to the public, with the goal of providing "a reliable and unambiguous form of music identification." In practice, that means you can look up music information, tag your own files, build applications on top of the database, and query it programmatically through the API or Live Data Feed. The main condition to keep in mind is licensing: the data is open, but it comes with data licenses you should read before redistributing or building on it.

Look up and identify music

The core use is identification. MusicBrainz organizes music metadata around entity types that appear throughout the site:

  • Artist
  • Event
  • Recording
  • Release
  • Release group
  • Series
  • Work
  • Area
  • Instrument
  • Label
  • Place

Because the goal is unambiguous identification, the same recording or release can be referenced consistently by both people and machines — useful when you need to match a track across different sources rather than relying on free-text titles alone.

Tag your music files

If your goal is cleaning up a local music library, MusicBrainz points to tagging tools rather than requiring you to edit metadata by hand:

  • MusicBrainz Picard — the project's own tagger
  • AudioRanger
  • Mp3tag
  • Yate Music Tagger

These tools use MusicBrainz metadata to identify and tag your files. The typical flow is: point the tool at your files, let it match them against MusicBrainz, review the matches, then write the tags. The common snag is mismatches on compilations, live versions, or releases with many pressings — check the suggested release before saving.

Build applications on the database

For developers, MusicBrainz offers several entry points:

Resource What it's for
MusicBrainz API Querying MusicBrainz data programmatically
Live Data Feed Consuming ongoing edits/changes
MusicBrainz Database Accessing the underlying database for building applications
MusicBrainz Server The server software itself

The site also lists developer resources alongside these. If you need bulk data rather than per-request queries, the database is the relevant path; if you need to react to changes as they happen, the Live Data Feed is the relevant path.

Contribute back

MusicBrainz is maintained by a global community, and the site explicitly invites participation. If you want to add or correct data, the starting points are the Beginners guide, Editing introduction, and Style guidelines, plus specific how-tos such as "How to add artists" and "How to add releases." Community channels include the forums and bug tracker.

Before you reuse the data

Check the Data licenses page linked in the site footer, along with the social contract and data removal policy. These govern how the data may be used and what obligations come with it. The project is operated by the MetaBrainz Foundation, a California-based 501(c)(3) tax-exempt non-profit, and describes itself as dedicated to keeping MusicBrainz free and open source — but "open" here means open licenses, so read them rather than assuming no conditions apply.

What Is MusicBrainz?

MusicBrainz is an open music encyclopedia that collects music metadata and makes it available to the public. It is maintained by a global community of users, similar to how Wikipedia works, and its data is released under open licenses. If you want a reliable, unambiguous way to identify music — for your own library, for an app, or for research — MusicBrainz is built for that purpose.

What MusicBrainz actually does

MusicBrainz is not a streaming service or a store. It is a database of information about music. Its stated goals are:

  • To be the ultimate source of music information by allowing anyone to contribute and releasing the data under open licenses.
  • To be a universal lingua franca for music by providing a reliable and unambiguous form of music identification, enabling both people and machines to have meaningful conversations about music.

The second point is the practical one for most users: MusicBrainz assigns stable identifiers to artists, releases, recordings, and other entities, so different systems can refer to the same piece of music without ambiguity.

What kind of data it holds

The site's navigation and database structure show the entity types it catalogs:

Entity type Examples of what it covers
Artist Performers, bands, composers
Release / Release group Albums, singles, and their groupings
Recording Individual recorded tracks
Work The underlying composition
Label Record labels
Event Concerts and performances
Place, Area, Series, Instrument Venues, geographic areas, series, instruments

It also supports annotations, tags, and relationships between entities, which is how it captures connections like "this artist performed on this recording."

Who runs it

MusicBrainz is operated by the MetaBrainz Foundation, a California-based 501(c)(3) tax-exempt non-profit corporation dedicated to keeping MusicBrainz free and open source. That matters if you care about the long-term availability and licensing terms of the data you build on.

How to start using it

The site offers a Quick start path plus a Beginners guide, and the community section explains how to contribute. Common entry points:

  • Beginners guide — orientation for new users.
  • Editing introduction and Style guidelines — how to add or correct data consistently.
  • How to add artists and How to add releases — task-specific instructions.
  • FAQs — answers to common questions.

If your goal is tagging your own music files, the site points to tools including MusicBrainz Picard, AudioRanger, Mp3tag, and Yate Music Tagger. For developers, there are the MusicBrainz API, Live Data Feed, and the MusicBrainz Database itself.

When MusicBrainz is the right choice

  • You need open-licensed music metadata you can reuse.
  • You want stable identifiers to match music across systems.
  • You are willing to rely on community-maintained data, with the same trade-offs as any wiki: broad coverage and open editing, but quality varies by entry.
  • You want to contribute corrections rather than only consume data.

If you need a commercial catalog with guaranteed completeness or a consumer playback service, MusicBrainz is a different kind of tool — it is a metadata source and community project, not a music service.

Website Overview

Limited stack disclosure and few obvious backend markers suggest a more restrained public footprint. That reduces easy fingerprinting clues but is not proof of overall security. 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 26 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 Gandi SAS, a widely used domain service provider. The domain uses the common .org extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by gandi.net, indicating managed DNS hosting. MX records point to the Google Workspace email service. CAA records restrict which certificate authorities are authorized to issue certificates. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown.

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 is valid for about 198 days in total, with 196 days remaining. The SAN includes a wildcard covering multiple hostnames at the same subdomain level. Shared private keys can increase the impact of a compromise.

HTTP and Browser Security

The response lacks these common security headers: HSTS, CSP, X-Content-Type-Options, Permissions-Policy, clickjacking protection. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header contains the custom value Plack::Handler::Starlet. Cookie security attributes are unknown.

Technology Stack Analysis

No obvious technology stack is exposed. This may reflect restrained information disclosure, although the underlying technologies remain unknown.

Search and Social Sharing

No homepage meta description was detected, leaving snippet selection more dependent on page text. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. No Open Graph metadata was detected, so social previews may depend on platform inference. The title has 41 characters, within a common display range. The observed directives allow indexing and link following.

Hosting and Email

DNSgandi.net
HostingHetzner Online GmbH
EmailGoogle Workspace
Location Germany flagFalkenstein, Saxony, Germany 142.132.241.153

User reviews (0)

  • No reviews yet.

Pages, Search and Sharing

Meta descriptionNot detected
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

Unknown

All bots 0 allowed · 35 disallowed
  • Disallow/account/
  • Disallow/admin
  • Disallow/ajax/
  • Disallow/area/
  • Disallow/cdstub/
  • Disallow/cdtoc/attach
  • Disallow/collection/
  • Disallow/edit/
  • Disallow/*/edits
  • Disallow/election/
  • Disallow/elections
  • Disallow/isrc/
  • Disallow/iswc/
  • Disallow/login
  • Disallow/oauth2
  • Disallow/otherlookup
  • Disallow/partners/
  • Disallow/rating/
  • Disallow/recording/
  • Disallow/register
  • Disallow/report/
  • Disallow/reports
  • Disallow/search
  • Disallow/set-beta-preference
  • Disallow/set-language/
  • Disallow/tag/
  • Disallow/taglookup
  • Disallow/tags
  • Disallow/test/
  • Disallow/toggle-legacy-browser
  • Disallow/tops/
  • Disallow/track/
  • Disallow/url/
  • Disallow/user/
  • Disallow/ws
  • IntervalCrawl delay 2 seconds
ia_archiver 1 allowed · 0 disallowed
  • Allow/
  • IntervalCrawl delay 1 seconds
ahrefsbot 0 allowed · 1 disallowed
  • Disallow/
crazywebcrawler-spider 0 allowed · 1 disallowed
  • Disallow/
semrushbot 0 allowed · 1 disallowed
  • Disallow/
semrushbot-sa 0 allowed · 1 disallowed
  • Disallow/
dotbot 0 allowed · 1 disallowed
  • Disallow/

Registration details RDAP / WHOIS

RegistrarGandi SAS
Registered2000-07-17
Expires2029-07-17
Domain statusclient transfer prohibited
Nameserversns-150-b.gandi.net、ns-198-c.gandi.net、ns-59-a.gandi.net
DNSSECunsigned

DNS records

TypeNameValueTTLPriority
Amusicbrainz.org142.132.241.153145—
AAAAmusicbrainz.org2a01:4f8:c011:f68::1138—
MXmusicbrainz.orgaspmx.l.google.com288001
MXmusicbrainz.orgalt1.aspmx.l.google.com288005
MXmusicbrainz.orgalt2.aspmx.l.google.com288005
MXmusicbrainz.orgalt3.aspmx.l.google.com2880010
MXmusicbrainz.orgalt4.aspmx.l.google.com2880010
NSmusicbrainz.orgns-150-b.gandi.net10800—
NSmusicbrainz.orgns-198-c.gandi.net10800—
NSmusicbrainz.orgns-59-a.gandi.net10800—
TXTmusicbrainz.orggoogle-site-verification=G4fF3tLLdINKF_4i0uJim28YqjjcD9Cwj6d5SJXAQxE10800—
TXTmusicbrainz.orgv=spf1 mx a ip4:138.201.203.0/26 ip4:138.201.228.89 include:_spf.google.com ~all10800—
CAAmusicbrainz.org0 issue "comodoca.com"10800—
CAAmusicbrainz.org0 issue "digicert.com"10800—
CAAmusicbrainz.org0 issue "letsencrypt.org"10800—
CAAmusicbrainz.org0 issue "sectigo.com"10800—
CAAmusicbrainz.org0 issuewild "digicert.com"10800—
CAAmusicbrainz.org0 issuewild "sectigo.com"10800—
DMARC_dmarc.musicbrainz.orgv=DMARC1; p=none; sp=none; adkim=r; aspf=r; rua=mailto:[email protected]; psd=y; t=n10800—

TLS and certificates

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subject*.musicbrainz.org
IssuerGandi SAS
Valid until2027-04-07T23:59 · Remaining when checked: 196 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HeaderValue
content-typetext/html; charset=utf-8
cache-controlno-transform
serverPlack::Handler::Starlet
referrer-policyunsafe-url
set-cookieRedacted

Identified technologies

Technology stack: Unknown

Recent Updates

  • Website images
  • Screenshots
  • Network details
  • Website Technologies
  • Pages and Search Information