How to Spot Holocaust Denial in Someone's Posts

Nobody serious types "the Holocaust never happened" anymore. It gets the post pulled and the account reported, and the people pushing the idea know it. So the claim learned to crouch. It comes out as a question about the numbers, a link to "research they don't want you to see," a smirking meme that means exactly what it looks like while leaving a back door open to say it was only a joke.

That crouch is what makes it hard to call from a single post. You are trying to separate a badly informed history take from a worldview that has decided six million is a lie. This guide is about doing that fairly - the moves denial actually makes now, the tropes it rides in on, and where the line sits between a real question and a rehearsed one.

Why Holocaust denial keeps mutating

Denial is old, organized and patient. For decades it was built into pamphlets, fake "institutes" and staged "debates," all designed to look like scholarship while smuggling in the lie. That scaffolding is why it can shed the swastika and still work: strip the slur, keep the doubt. "I'm just asking why we're not allowed to question it" does the job the open claim used to do, and it does it without tripping the obvious filters.

It also rarely shows up on its own. Denial is usually one room in a bigger house of antisemitic conspiracy - the same claims about who really controls money, media and governments, now with an extra move: casting the historical record itself as part of the plot. Online hate is not a fringe corner of the internet, either. The ADL found that 56% of Americans say they have experienced online hate or harassment in their lifetime (ADL, 2024). Some of what you are learning to read is aimed at other people; some of it is being tried out on you.

What it looks like in a feed

It runs on a spectrum, and it helps to know the whole range before you judge any one post.

• The blunt end. Flat denial, "it's a hoax," open contempt aimed at Jewish people, cartoons that recycle the old caricatures. Rare on the big platforms because it gets pulled, but it still surfaces, and it leaves no room for a charitable reading.
• The "just asking questions" layer. The real workhorse. Not a claim but a pose - "why can't we examine it," "do your own research," "follow the money on who wrote the textbooks." It never commits, so it is always deniable, and that is the point.
• The number game. Nitpicking the death toll, insisting the figure was "revised," treating a documented genocide like a spreadsheet with suspicious rounding. The aim is not accuracy; it is to shrink an atrocity until it feels arguable.
• The joke layer. Irony as cover - a meme, an oven "gag," a reply that plays the crime for a laugh. One is deniable. A steady diet of them is a worldview wearing a grin.

Worth saying plainly, because this is where fairness matters most: real historical questions exist, and historians argue about detail all the time. The difference is direction. A genuine question is trying to understand what happened; denial is trying to make it disappear. When someone only ever "asks" in ways that chip at the fact of the genocide, and never once at their own doubt, the questions are not questions.

How to spot Holocaust denial in someone's posts

The single most useful habit is to stop reading posts as isolated events. Denial is a position, and a position shows up as repetition. The same "question" phrased three different ways across a year, the same fake sources quoted approvingly, the same replies cheering it on - that is signal. A lone strange line, with nothing like it around it, usually is not.

Then read the company someone keeps. People stay careful in their own posts and get careless in the replies, so scroll the comments they leave and the accounts they boost. Read across platforms, too, because the version that stays polite on LinkedIn drops the act on a burner-feeling X account. When the coded "just asking" on one site lines up with something blunter somewhere else, the deniability is gone.

A reading checklist

1. Start with the plain words of a post, then ask who else uses that phrase and what they mean by it.
2. Learn the recurring moves - 'just asking questions' about the numbers, claims the evidence was faked, mockery dressed as a meme.
3. Watch for the antisemitic conspiracy tropes that denial usually travels with, and for coded numbers and symbols.
4. Read the replies and reposts, not only the original post, because the blunt version often shows up in the comments.
5. Check whether it appears once or runs through months of the timeline across X, TikTok, Instagram, Facebook and LinkedIn.
6. Keep the actual post as evidence and let your own judgement, in context, make the final call.

The honest limits

Be straight about what a read like this can and cannot do. It sees public posts only - locked accounts, private groups and DMs are out of reach - and it only has something to work with if the person actually posts. A quiet timeline tells you very little either way.

And context is where automated flagging struggles most. A historian's thread, a survivor's testimony quoted in full, a teacher explaining the crime, someone repeating a denier's line precisely to demolish it - all of it can trip a filter that reads words faster than it reads intent. That is exactly why a flag should arrive with the post attached: it is a reason to look, not a verdict handed down. You read it in context and decide. A clean result means nothing in the public posts stood out - not that a person has been cleared, and not that they are safe.

Used that way, a read is not about catching people out. It is about not being the last to know what someone has been saying, in the open, the whole time.