SS-ZVH4F

test

Download
Sign in for full quality Sign in to download sealed file Sign in to download seal PNG

test

test

41 views
Is this AI? Very Likely AI Generated The file history identifies generative AI, even though the source declared no AI use.
Why this answer? A plain-language summary with more detail available below
KEY EVIDENCE

Why SourceSeal reached this answer

High confidence
  • The file history explicitly records generative AI.
  • The source declaration conflicts with the file history.
Declaration conflict

The source declared “No AI Used,” but file-bound provenance identifies generative AI creation. File history takes priority for the AI answer, and the contradiction lowers media trustworthiness.

Estimated AI likelihood 96% 88% evidence confidence
Source reliability Somewhat Trustworthy 52% source score
Source declaration No AI Used Conflicts with the available file history.
File history AI origin recorded — integrity problem The history records generative AI. A file-bound check did not match, which affects trust in the record but not the AI-origin signal.
Media trustworthiness details Not Trustworthy · 20%

How media trustworthiness was calculated

No community ratings have been submitted, so the result relies on the source declaration, file history, metadata, and verified source identity.

Not Trustworthy 20% score
Base score 50%
neutral start

Each media item starts near neutral. File-history, source identity, and community evidence then move the score up or down.

Content Credentials Integrity problem
-35 points

A signature, asset hash, assertion reference, file binding, or ingredient binding did not match.

File metadata No useful fields
no direct change

Only basic encoding data was available, or no privacy-safe capture/processing metadata was found.

Source identity 56% source baseline
+4.8 points

Verified connected accounts and follower reach, email and source verification, account age, and plan continuity establish identity reliability. These signals carry more weight and make small on-site vote samples less influential, but they never override contradictory file history.

AI-use declaration 60% concern
shown as AI concern

The available file history lists the digital source as Generative AI media, but the Content Credentials did not fully validate. SourceSeal shows this as an AI declaration concern, while treating it as weaker than a validated mismatch.

Community ratings No ratings yet
no direct change

No viewers have rated this media yet. The displayed score is therefore based on file-history, metadata, and source identity signals.

Final score 20%
file history starting score

No community ratings have been submitted yet, so this score is the file-history and source-identity starting score.

File history and metadata AI origin recorded — integrity problem
AI origin recorded — integrity problem

The history records generative AI. A file-bound check did not match, which affects trust in the record but not the AI-origin signal.

Checked Aug 19, 2026 3:36 AM
Digital source
Generative AI media
Signer
OpenAI Media Service
Certificate issuer
OpenAI OpCo, LLC
Signature algorithm
Es256
Claim generator
OpenAI Media Service API
Signed
Jun 4, 2026 8:55 PM
Manifest chain
1 manifest · 0 ingredients

Recorded actions

  1. Created Jun 4, 2026 12:00 AM · gpt-image 2.0
  2. Converted Jun 4, 2026 12:00 AM
  3. Watermarked.unbound Jun 4, 2026 12:00 AM

Manifest chain

image.png Active

OpenAI Media Service API

OpenAI Media Service

Validation details

  • signingCredential.untrusted signing certificate untrusted
  • signingCredential.untrusted
  • self#jumbf=/c2pa/urn:c2pa:6bf0b337-85af-42f8-af4e-11db2c9d9034/c2pa.signature
  • signing certificate untrusted
  • signingCredential.ocsp.notRevoked certificate not revoked
  • signingCredential.ocsp.notRevoked
  • OCSP_RESPONSE
  • certificate not revoked
  • timeStamp.validated timestamp message digest matched: OpenAI TSA Leaf
  • timeStamp.validated
  • timestamp message digest matched: OpenAI TSA Leaf
  • claimSignature.insideValidity claim signature valid
  • claimSignature.insideValidity
  • claim signature valid
  • claimSignature.validated claim signature valid
  • claimSignature.validated
  • assertion.hashedURI.match hashed uri matched: self#jumbf=c2pa.assertions/c2pa.icon
  • assertion.hashedURI.match
  • self#jumbf=/c2pa/urn:c2pa:6bf0b337-85af-42f8-af4e-11db2c9d9034/c2pa.assertions/c2pa.icon
  • hashed uri matched: self#jumbf=c2pa.assertions/c2pa.icon
  • assertion.hashedURI.match hashed uri matched: self#jumbf=c2pa.assertions/c2pa.actions.v2
  • self#jumbf=/c2pa/urn:c2pa:6bf0b337-85af-42f8-af4e-11db2c9d9034/c2pa.assertions/c2pa.actions.v2
  • hashed uri matched: self#jumbf=c2pa.assertions/c2pa.actions.v2
  • assertion.hashedURI.match hashed uri matched: self#jumbf=c2pa.assertions/c2pa.certificate-status
  • self#jumbf=/c2pa/urn:c2pa:6bf0b337-85af-42f8-af4e-11db2c9d9034/c2pa.assertions/c2pa.certificate-status
  • hashed uri matched: self#jumbf=c2pa.assertions/c2pa.certificate-status
  • assertion.hashedURI.match hashed uri matched: self#jumbf=c2pa.assertions/c2pa.hash.data
  • self#jumbf=/c2pa/urn:c2pa:6bf0b337-85af-42f8-af4e-11db2c9d9034/c2pa.assertions/c2pa.hash.data
  • hashed uri matched: self#jumbf=c2pa.assertions/c2pa.hash.data
  • assertion.dataHash.match data hash valid

Source

Test account

This source has not added a bio yet.

Total views241
Public seals7
Source reliability Somewhat Trustworthy

52% based on verified identity, audience reach, and evidence across sealed media.

View full source page

Focused discussion

0 comments and replies about whether this media is real, AI-generated, or missing context.

Sign in to comment, like useful notes, and reply to a thread.

No discussion yet.