Website profiles · Technology insights · Alternatives

place-atlas.stefanocoding.me

Place Atlas Initiative is a group that hosts the r/place Atlas projects and others.

No paid content found
Visit website
Profile views 2 Outbound visits 1 Normal
Place Atlas Initiative Full homepage screenshot

At a glance

Category
Games & Board Games
Language
English
Paid-content signal
No paid content foundObserved
Registered
Unknown
Hosting
NetlifyInferred
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 Place Atlas Initiative?

Place Atlas Initiative is a volunteer group that documents the collaborative pixel canvases known as r/place. Its stated approach is "Documenting as it is, not as we want" — an archival mindset, not a curation or ranking one. The group hosts atlas projects for multiple r/place editions (2017, 2022, 2023), a related r/place Wiki, and affiliated efforts such as The Final Clean and the 2022 r/place Catalog.

What the atlases actually do

Each atlas maps the finished canvas: which community drew which area, what the artwork depicted, and the stories behind alliances, raids and overwrites. That makes the projects useful in three concrete ways:

  • Finding your own corner. If you placed pixels for a subreddit in 2022, the atlas is where you check how your section was labelled and whether the entry matches what you remember.
  • Research and journalism. Writers, students and data-visualisation hobbyists use the atlases as a reference for community coordination on Reddit.
  • Preservation. Reddit's live canvas is temporary; the atlases keep a described, annotated version after the event ends.

Who it is for

Historians of internet culture, r/place participants, and moderators of communities that organised pixel art. It is less useful if you want live canvas data, tooling to draw on a current event, or a general Reddit history resource — the scope is specifically r/place and closely related archives.

How the work is organised

The team splits into archival, development and wiki groups, with a project leader. That division matters practically: corrections to a label go through wiki and archival contributors, while site bugs belong with the development side. If you spot an error in an atlas entry, checking the wiki first is usually the faster route, since the wiki often holds the discussion behind a label.

A note on reliability

Because entries are community-written, treat any single label as a claim rather than a fact — cross-check against the wiki page or the community's own records. The atlas is strongest on broad geography and well-known artworks, and thinner on small, short-lived drawings that were overwritten before anyone documented them.

For a quick start, open the atlas for the edition you care about and search for the subreddit or the coordinates you remember; if the entry looks wrong, the wiki is the place to compare notes.

How can I access the r/place Atlas for a specific year like 2017, 2022, or 2023?

The Place Atlas Initiative publishes separate atlases for each major r/place event, so you reach a specific year through its own project page rather than one combined viewer. Start at the initiative's site, Place Atlas Initiative, and choose the year you want from the Projects list: the 2017 atlas (continued), the 2022 atlas, or the 2023 atlas.

What each year covers

Year Where it lives Practical use
2017 Listed as "continued," with a separate legacy version under Affiliated Projects Comparing the original canvas with later community annotations
2022 Its own atlas project The largest, most heavily documented canvas, useful for pixel-by-pixel lookups
2023 Its own atlas project Research on the most recent canvas before the initiative's 2023 snapshot

Two related resources sit alongside the atlases: the r/place Wiki and, under Affiliated Projects, The Final Clean and the 2022 r/place Catalog. The Catalog is the one to check when you want a structured listing of 2022 artworks rather than an interactive map.

A concrete way to use it

Suppose you are writing about a specific 2022 artwork and need its coordinates, creator, and description. Open the 2022 atlas, locate the region on the canvas, and read the entry attached to that area; then cross-check the same piece in the 2022 Catalog if you need a second listing. For a 2017 comparison, do the same on the 2017 atlas and note that the legacy version under Affiliated Projects may differ in coverage or annotation style.

If you are unsure which year to open, decide from the event: 2017 for the original experiment, 2022 for the expanded canvas most people mean when they say "the r/place Atlas," and 2023 for the most recent event. Each project page is the authoritative entry point for its own year.

What is the difference between the Place Atlas Initiative's projects and its affiliated projects?

The Place Atlas Initiative separates work it runs directly from outside projects it chooses to recognize. Its own projects are the r/place Atlases and the r/place Wiki; the affiliated list points to efforts like the legacy 2017 Atlas, The Final Clean, and the 2022 r/place Catalog, which the Initiative acknowledges but does not present as its own. In practice, the main distinction is editorial responsibility: the Initiative's team organizes, documents and maintains its own projects, while affiliated projects remain under other people's stewardship.

How to read the two lists

  • Projects — the Initiative's active, continuing documentation work. The 2017 Atlas is marked as continued, alongside the 2022 and 2023 Atlases and the r/place Wiki.
  • Affiliated Projects — related resources that sit outside that direct line, including the legacy 2017 Atlas, The Final Clean and the 2022 r/place Catalog.

What that means if you use the site

If you want the Initiative's current documentation, start with its own projects. If you need an older or complementary resource, the affiliated list is where to look, but expect a different maintainer and possibly different methods or coverage.

The Initiative's stated approach, "Documenting as it is, not as we want," is a useful decision criterion: prefer the project whose documentation matches that aim for your question, whether it is the current Atlases, the Wiki, or an affiliated catalog. For a concrete case, someone researching a 2022 canvas region would begin with the Initiative's 2022 Atlas and then check the affiliated 2022 Catalog for a second, independently maintained view.

Who is on the Place Atlas Initiative team and what roles do they have?

The Place Atlas Initiative names its team by project area rather than by formal job title. The site lists four groups:

Role People listed
Project Leader TCOOfficiall (Stefano Haagmans)
Archival Team AnonymousRandPerson, tycho (electric-blue), Nick12 (Nico Abram), m654zy
Development Team Hans5958 (Hans5958_), prosto_sanja (Alex Tsernoh), mxdanger
Wiki Team Aeywoo (xXLInkster17Xx), Nick12, pax, Artillect, axollyon, Crzka (Cappy Ishihara), CodeDev, dntk (treeway7), Eurobat, FuriousChocolate, geekahedron, samurai_crusader (Jim Milton), Noah (NoahS04), Saya (sayaduck), Sodapone, dreamingkills (tea), Zurke

A few practical notes for reading this roster. Nick12 appears in both the Archival and Wiki teams, so the groups overlap rather than being strictly separate departments. The Project Leader role is a single named person, which suggests coordination and representation duties sit with one individual, while the archival, development and wiki work is distributed across larger groups.

If you need to attribute or credit work, the safest approach is to name the specific team rather than the whole initiative, since a person's involvement may be limited to one area. If you are looking for a contact about a particular dataset, tool or wiki page, start with the team whose remit matches that output, and check the project pages linked from Place Atlas Initiative for any more current listing, since team membership can change over time.

How can I contribute to the r/place Atlas or the r/place Wiki?

The Place Atlas Initiative's own site lists both the r/place Atlases and the r/place Wiki as active projects, with a named team split into archival, development and wiki work. That structure is the best guide to how you can help: contributions are organised by project and by skill, rather than through a single general form.

Ways to help, by project

  • The r/place Atlases (2017, 2022, 2023). These are the annotated maps of the canvas. Useful contributions include identifying unnamed artwork, correcting a label, supplying the origin or community behind a piece, and pointing out entries that were misread. If you were part of a community that drew something on the canvas, you are often the best source for what it was and why it existed.
  • The r/place Wiki. This is written documentation rather than map annotation — articles on artworks, communities, events and the wider history of each canvas. Writing, copy-editing, adding references and filling gaps in existing articles all fit here.
  • Archival work. The initiative keeps a dedicated archival team, which tells you that preserving screenshots, timelapses, threads and other primary material is treated as its own job. If you saved captures during an event, that material has value even if you never write a word of prose.
  • Development. The site lists a separate development team, so technical work — tooling, the site itself, data handling for the atlases — is a distinct track from research or writing.

How to start

Go to the initiative's site and look at the project you actually care about, then find how that specific project takes contributions — the Atlases, the Wiki and the affiliated projects each have their own communities and channels. A short, specific offer works better than a general one: name the artwork or article, say what is wrong or missing, and give your source. If you have no source, say so plainly and describe what you remember or witnessed; that is still useful for a wiki editor to weigh.

Choosing where to put your effort

If you… Start with
Know a specific artwork and its community The relevant year's Atlas
Enjoy writing and citing The r/place Wiki
Saved screenshots or recordings Archival work
Can build or maintain tools Development

The trade-off is depth versus reach. Fixing one label on an Atlas is quick and immediately visible; writing a wiki article takes longer but captures context an annotation cannot hold. Doing both for the same artwork — a corrected map entry plus a short article — is usually the most valuable single contribution a knowledgeable participant can make.

What is the purpose of The Final Clean and The 2022 r/place Catalog?

The Final Clean and The 2022 r/place Catalog are affiliated projects listed by the Place Atlas Initiative, a group that hosts r/place Atlas projects and related documentation. Both sit alongside the main Atlas work rather than replacing it: the Initiative describes its approach as documenting the canvas “as it is, not as we want,” which is a useful way to understand why these side projects exist.

The Final Clean

The name suggests a cleanup or finalised version of r/place documentation. In practice, a project like this is usually for people who want a tidier reference than a live, constantly edited atlas: a resolved or consolidated view of the canvas after the event, rather than an in-progress record. That makes it most useful for readers who care about the end state of a canvas, not the editing history.

The 2022 r/place Catalog

A catalog is typically an index or organised listing rather than a map. For r/place, that likely means a structured way to browse or locate entries from the 2022 event, which helps when you know roughly what you are looking for but not where it sits in a larger Atlas. It complements the 2022 r/place Atlas, which is the Initiative's main project for that year.

How to choose between them

  • If you want the finished, cleaned-up record of a canvas, start with The Final Clean.
  • If you want to browse or look up 2022 entries in an organised way, start with The 2022 r/place Catalog.
  • If you want the Atlas itself, the Initiative lists the 2017, 2022 and 2023 Atlases plus the r/place Wiki as its core projects.

A practical next step: open the Initiative's projects list and note which entries are marked as affiliated versus core. Affiliated projects are often smaller in scope, so treat them as companions to the Atlas rather than substitutes. The r/place Wiki at Place Atlas Initiative is the natural starting point for cross-checking what each project covers.

Related questions

More questions →
Who Is Behind the Place Atlas Initiative?

The Place Atlas Initiative is led by TCOOfficiall (Stefano Haagmans), who is listed as Project Leader. The work is distributed across three teams — Archival, Development, and Wiki — that together maintain the r/place Atlas projects and the r/place Wiki. If you want to know who to credit, contact, or follow for a specific part of the Atlas, the team breakdown below is the place to start.

Project leadership

Role Person
Project Leader TCOOfficiall (Stefano Haagmans)

The Initiative describes itself as a group that hosts the r/place Atlas projects and others, with the stated approach of "Documenting as it is, not as we want."

The three teams

Archival Team

  • AnonymousRandPerson
  • tycho (electric-blue)
  • Nick12 (Nico Abram)
  • m654zy

This team handles the archival side of the projects — the work of preserving and organizing what gets documented.

Development Team

  • Hans5958 (Hans5958_)
  • prosto_sanja (Alex Tsernoh)
  • mxdanger

This team covers the technical build of the Atlas sites and related tooling.

Wiki Team

  • Aeywoo (xXLInkster17Xx)
  • Nick12
  • pax
  • Artillect
  • axollyon
  • Crzka (Cappy Ishihara)
  • CodeDev
  • dntk (treeway7)
  • Eurobat
  • FuriousChocolate
  • geekahedron
  • samurai_crusader (Jim Milton)
  • Noah (NoahS04)
  • Saya (sayaduck)
  • Sodapone
  • dreamingkills (tea)
  • Zurke

The Wiki Team is the largest of the three, which fits the scale of writing and maintaining wiki content across multiple r/place years.

What the teams maintain

The Initiative's projects and affiliated projects give the teams their scope:

Projects

  • The 2017 r/place Atlas (continued)
  • The 2022 r/place Atlas
  • The 2023 r/place Atlas
  • The r/place Wiki

Affiliated Projects

  • The 2017 r/place Atlas (legacy)
  • The Final Clean
  • The 2022 r/place Catalog

Note that Nick12 (Nico Abram) appears on both the Archival Team and the Wiki Team, so the team lists are not strictly exclusive.

Practical takeaways

  • For attribution or credit: start with TCOOfficiall as Project Leader, then route to the specific team that owns the work.
  • For archival questions: the Archival Team is the relevant group.
  • For site bugs or technical issues: the Development Team.
  • For wiki content, corrections, or additions: the Wiki Team.

The site footer carries a © 2023 notice and notes a site repository, so the codebase itself is a separate track from the team rosters above.

What do the r/place Atlas projects document?

The r/place Atlas projects document the pixel art and community creations that appeared on Reddit's r/place canvases. They annotate each artwork with information about what it depicts, who made it, and the stories behind it, creating a historical record of these collaborative events. The Place Atlas Initiative hosts Atlases for the 2017, 2022, and 2023 r/place events, along with related archival projects.

What the Atlases actually record

Each Atlas is an interactive map layered over a snapshot of an r/place canvas. Rather than just preserving the raw image, the Atlas adds context that the pixels alone can't convey:

  • Artwork identification – what each drawing or logo represents
  • Attribution – which communities, subreddits, or groups created it
  • Descriptions – background on the design, its meaning, or the coordination behind it
  • Positional data – where on the canvas each piece was placed

This turns a static image into a browsable, searchable archive of community effort.

Coverage across r/place events

The Initiative maintains Atlases for multiple editions of r/place:

Project Event documented
The 2017 r/place Atlas (continued) 2017 canvas
The 2022 r/place Atlas 2022 canvas
The 2023 r/place Atlas 2023 canvas
The r/place Wiki Supporting wiki content

A legacy version of the 2017 Atlas also exists as an affiliated project, reflecting how the documentation effort has evolved over time.

Why these projects exist

r/place canvases are temporary. Once an event ends, the collaborative artwork is no longer live, and without documentation the context — who built what and why — is easily lost. The Atlas projects exist to preserve that history, guided by the Initiative's stated principle of "Documenting as it is, not as we want." The goal is an accurate record of what communities actually created, not an idealized version.

Affiliated and related projects

Beyond the main Atlases, the Initiative lists affiliated efforts that support the same archival mission:

  • The 2017 r/place Atlas (legacy) – the earlier version of the 2017 documentation
  • The Final Clean – a related archival project
  • The 2022 r/place Catalog – a catalog tied to the 2022 event

These complement the Atlases by capturing additional angles on the same events.

Who runs it

The Place Atlas Initiative is organized by a project leader, TCOOfficiall (Stefano Haagmans), supported by archival, development, and wiki teams. Contributors include AnonymousRandPerson, Hans5958, Aeywoo, and others listed across the Initiative's team sections. The site itself is maintained through a public repository.

If you want to explore a specific r/place year or look up a particular artwork, start with the Atlas for that event and use its map interface to browse annotated regions.

What projects and affiliated projects are part of the Place Atlas Initiative?

The Place Atlas Initiative hosts two groups of work: Projects and Affiliated Projects. The Projects section lists the atlases and wiki it currently maintains, while Affiliated Projects lists related efforts that sit alongside them. All of these are reachable from the Initiative's site at place-atlas.stefanocoding.me.

Projects

These are the entries listed under the site's "Projects" heading:

Project Notes
The 2017 r/place Atlas (continued) The ongoing version of the original 2017 atlas
The 2022 r/place Atlas Atlas covering the 2022 canvas
The 2023 r/place Atlas Atlas covering the 2023 canvas
The r/place Wiki Wiki companion to the atlas work

The "(continued)" label on the 2017 atlas distinguishes it from the legacy 2017 atlas listed under Affiliated Projects — the Initiative treats the continued version as a current project and the older one as affiliated.

Affiliated Projects

These are listed separately under "Affiliated Projects":

  • The 2017 r/place Atlas (legacy) — the earlier version of the 2017 atlas
  • The Final Clean — an affiliated effort listed alongside the atlases
  • The 2022 r/place Catalog — a catalog tied to the 2022 canvas

How to use this list

If you want the current atlas for a given canvas year, start with the Projects list — 2017 (continued), 2022, and 2023 are all there, plus the r/place Wiki. If you specifically need the older 2017 atlas, the 2022 catalog, or The Final Clean, look under Affiliated Projects instead. The site itself is the entry point for all of them; the page does not describe separate login requirements or pricing for any project.

Who runs them

The Initiative credits a Project Leader, TCOOfficiall (Stefano Haagmans), supported by an Archival Team, a Development Team, and a Wiki Team. The site footer carries the line "From Place Atlas Initiative, with care." and a 2023 copyright notice, with a link to the site repository.

What Is the Place Atlas Initiative?

The Place Atlas Initiative is a group that hosts the r/place Atlas projects and other related efforts. Its stated approach is "Documenting as it is, not as we want" — meaning the focus is on recording what actually appeared on the r/place canvas rather than curating or reinterpreting it. If you want to understand who maintains the r/place Atlases, what projects fall under the group, or how the team is organized, this covers what the site itself documents.

What the Initiative Does

The Initiative is best understood as an umbrella organization for documentation projects tied to Reddit's r/place events. Rather than producing a single tool, it maintains multiple Atlases across different years and a companion wiki. The guiding principle quoted on the site — "Documenting as it is, not as we want" — signals that the Atlases aim to be archival records of the canvas, not editorialized versions of it.

Core Projects

The site lists the following as its projects:

  • The 2017 r/place Atlas (continued) — an ongoing version of the original 2017 Atlas
  • The 2022 r/place Atlas
  • The 2023 r/place Atlas
  • The r/place Wiki

These represent the Initiative's main documentation output across the three r/place events it covers.

Affiliated Projects

Alongside its own projects, the Initiative lists affiliated efforts:

  • The 2017 r/place Atlas (legacy) — the earlier version of the 2017 Atlas
  • The Final Clean — a related project
  • The 2022 r/place Catalog

The distinction matters if you're looking for a specific version of an Atlas: the "continued" 2017 Atlas is a current Initiative project, while the "legacy" 2017 Atlas is listed separately as affiliated.

How the Team Is Organized

The site groups its team into four functional areas:

Team Members listed
Project Leader TCOOfficiall (Stefano Haagmans)
Archival Team AnonymousRandPerson, tycho (electric-blue), Nick12 (Nico Abram), m654zy
Development Team Hans5958 (Hans5958_), prosto_sanja (Alex Tsernoh), mxdanger
Wiki Team Aeywoo (xXLInkster17Xx), Nick12, pax, Artillect, axollyon, Crzka (Cappy Ishihara), CodeDev, dntk (treeway7), Eurobat, FuriousChocolate, geekahedron, samurai_crusader (Jim Milton), Noah (NoahS04), Saya (sayaduck), Sodapone, dreamingkills (tea), Zurke

The split suggests the work divides into preserving canvas data (Archival), building and maintaining the Atlas tools (Development), and writing/maintaining wiki content (Wiki), with overall coordination from the Project Leader.

What the Site Does Not Specify

The page evidence does not include pricing information, login requirements, or access restrictions for any of the projects. If you need to know whether a given Atlas or the wiki requires an account or payment, that isn't stated in the source material and would need to be checked directly on the relevant project.

Website Overview

An advisory match combined with missing browser safeguards may increase exposure if the affected component is active. Deployment-specific verification and remediation deserve priority. Identifiable technologies and additional version or configuration signals make the service easier to fingerprint, which may help targeted scanners narrow their checks.

Domain and Registration

Unknown

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the Zoho Mail email service. CAA records restrict which certificate authorities are authorized to issue certificates. SPF and DMARC are configured. DKIM status is unknown. TXT records include verification markers for Google, Atlassian, Meta, Microsoft. Such markers may also remain after a service stops being used.

TLS and Certificates

The public key uses EC with 256 bits. 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 by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, X-Content-Type-Options, Referrer-Policy, 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 Netlify. No explicit CDN or WAF marker was found in the response headers.

Technology Stack Analysis

The public page identifies Astro 3.1.3, Netlify, with exact versions exposed for 1 technologies. These details can narrow vulnerability checks, although exposure alone is not a vulnerability. The advisory source OSV places Astro 3.1.3 in the affected range of GHSA-26w7-cxv4-gfx2, GHSA-2pvr-wf23-7pc7, GHSA-376h-93r7-7g6f, GHSA-49w6-73cw-chjr, GHSA-4g3v-8h47-v7g6 等 10 项. Verify the deployed version and relevant configuration before drawing conclusions about exploitability. Updating affected components should be a priority.

Search and Social Sharing

The Generator tag identifies Astro v3.1.3, making the publishing system easier to fingerprint. No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. The title has 22 characters, within a common display range. A meta description is present, with 83 characters. The observed directives allow indexing and link following.

Hosting and Email

DNSCloudflare
HostingNetlify
EmailZoho Mail
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagAshburn, Virginia, United States Inferred 18.208.88.157

Registration details

RDAP / WHOIS

Unknown

DNS records

DNS

TypeNameValueTTLPriority
Aplace-atlas.netlify.app18.208.88.157120—
Aplace-atlas.netlify.app98.84.224.111120—
AAAAplace-atlas.netlify.app2600:1f18:16e:df01::258311—
AAAAplace-atlas.netlify.app2600:1f18:16e:df01::259311—
MXstefanocoding.memx.zoho.eu179910
MXstefanocoding.memx2.zoho.eu179920
MXstefanocoding.memx3.zoho.eu179950
NSstefanocoding.mebetty.ns.cloudflare.com86400—
NSstefanocoding.meterin.ns.cloudflare.com86400—
TXTstefanocoding.meMS=ms61739625300—
TXTstefanocoding.meMS=ms63877921300—
TXTstefanocoding.meatlassian-domain-verification=0WnuICzS3KnRBABiRyPCoLz2lLfYZjmy/zp1k7DNHeNIhaVsRqk2D9kkXrEkdZGx300—
TXTstefanocoding.meatlassian-sending-domain-verification=26db2721-a075-44e0-a14e-11a02ee3bffe300—
TXTstefanocoding.mefacebook-domain-verification=3n0z0yknr49bbbkrm7day31omakvt9300—
TXTstefanocoding.megoogle-site-verification=5uMxL2tX-4SqiKnEcfH90_Q7KPVd-js-xb75W-eVnfM300—
TXTstefanocoding.megoogle-site-verification=Hr4EQdmGPE6MDIkKyeXCW2d19f1Tq20nPKthl4tQ4oI300—
TXTstefanocoding.metcpshield-network-verification=AYLUMUJWJNZ5Z7DRH5TUT6EXD2GE6HJSGMGIMOU6GKTG4B46SVVQBPUWLUJO6YQXSKJTG3WR3J433QANF5FEXSVKYWDG2MF7BGFTM3A=300—
TXTstefanocoding.metiktok-developers-site-verification=3kKGilFGdWA02JDnkvCXXDIMR2RpQw2C300—
TXTstefanocoding.mev=spf1 include:zoho.eu include:mail.smtp2go.com include:sendgrid.net -all300—
TXTstefanocoding.mezoho-verification=zb15526538.zmverify.zoho.eu300—
CNAMEplace-atlas.stefanocoding.meplace-atlas.netlify.app300—
CAAstefanocoding.me0 issue "comodoca.com"3600—
CAAstefanocoding.me0 issue "digicert.com; cansignhttpexchanges=yes"3600—
CAAstefanocoding.me0 issue "letsencrypt.org"3600—
CAAstefanocoding.me0 issue "pki.goog; cansignhttpexchanges=yes"3600—
CAAstefanocoding.me0 issue "ssl.com"3600—
CAAstefanocoding.me0 issuewild "comodoca.com"3600—
CAAstefanocoding.me0 issuewild "digicert.com; cansignhttpexchanges=yes"3600—
CAAstefanocoding.me0 issuewild "letsencrypt.org"3600—
CAAstefanocoding.me0 issuewild "pki.goog; cansignhttpexchanges=yes"3600—
CAAstefanocoding.me0 issuewild "ssl.com"3600—
DSstefanocoding.me2371 13 2 0acde0a40fc7b7c91323b4a8105fb3dbe1862a17d6317ba826feb8dfa8e22a823600—
DMARC_dmarc.stefanocoding.mev=DMARC1; p=quarantine; rua=mailto:[email protected]; ruf=mailto:[email protected]; sp=quarantine; adkim=s; aspf=s300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectplace-atlas.stefanocoding.me
IssuerLet's Encrypt
Valid until2027-01-03T07:33 · Remaining when checked: 78 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=UTF-8
cache-controlpublic,max-age=0,must-revalidate
serverNetlify
strict-transport-securitymax-age=31536000

Identified technologies

Astro 3.1.3Netlify

Pages, Search and Sharing

Meta descriptionPlace Atlas Initiative is a group that hosts the r/place Atlas projects and others.
Canonical URLNot detected
LanguageEnglish (default)
Twitter CardNot detected

No robots.txt found

No sitemaps found

User reviews (0)

  • No reviews yet.