Sarai Hannah Ajai'sIONOS Domain Account, Google Email Account Access Failure, Suspected Credential Compromise, Suspected Unauthorized Apartment Entry, Possible Apple iPhone 17 Mirroring / Cloning Misuse, Ring and Wyze Camera Interference Concern, Recently Deleted Google Account Notice, and Request to Discontinue SurvivingTheSystemPodcast.com and Related Accounts
Incident Report
Subject
IONOS Domain Account, Google Email Account Access Failure, Suspected Credential Compromise, Suspected Unauthorized Apartment Entry, Possible Apple iPhone 17 Mirroring / Cloning Misuse, Ring and Wyze Camera Interference Concern, Recently Deleted Google Account Notice, and Request to Discontinue SurvivingTheSystemPodcast.com and Related Accounts
Reporting Party
Name: Sarai Hannah Ajai
Location: *****, ***** ******
Date of Report: May 25, 2026
Primary Domain Involved: survivingthesystempo
Domain Registrar / Provider: IONOS
Related Website: https://
Related Google Email Accounts:
Related Devices / Services: Apple iPhone 17, Google Account Recovery, Ring cameras, Wyze cameras, GitHub website files, IONOS domain account, Gmail account recovery services.
Purpose of Report:
To document suspected compromise of domain-related credentials, inability to regain access to related Google accounts through Google recovery, evidence of a recently deleted Google account notice, suspected unauthorized physical entry into Apartment Unit **5, possible interference with Ring and Wyze cameras through suspected Apple iPhone 17 mirroring / cloning access, and the reporting party’s request to preserve records and formally discontinue the domain name and related project accounts.
I. Executive Summary
On May 25, 2026, I, Sarai Hannah Ajai, attempted to access and recover Google email accounts associated with the domain name survivingthesystempodcast
On or about the same date, November 21, 2025, I created two Google email addresses for the domain and project:
These email accounts were intended to support the Surviving the System Podcast domain, website, and related online identity. After establishing the domain, a GitHub-based website was also created for the project.
After the website was created, I wrote the two Google email addresses and related login information on two index cards and placed them on top of my desk in Apartment Unit **5. I intended to transfer that information into my permanent log book, but I did not complete that step immediately because I was occupied with other web applications work.
I now believe that sometime between approximately December 15, 2025 and February 2026, while I briefly left my apartment unit, **5 to take out trash, one or more unauthorized persons may have entered my apartment and taken the two index cards from the top of my desk. I cannot identify the responsible person from the evidence presently available. However, I am documenting this as a suspected unauthorized physical-access and account-credential compromise event.
I also suspect that, during or around the suspected unauthorized entry, the person or persons involved may have used, accessed, or exploited my Apple iPhone 17 or a mirrored / cloned connection to my Apple iPhone 17 to interfere with my Ring and Wyze cameras. My concern is that camera recording, camera availability, motion detection, notifications, network access, or app-level access may have been disabled, paused, altered, or made unavailable without my consent or legal authorization. I cannot independently prove the exact technical method at this time, and I request technical review of Ring, Wyze, Apple, network, and device-access logs to determine whether camera activity was interrupted during the suspected entry window.
On May 25, 2026, I attempted to use Google’s account recovery tools to access the related Gmail accounts. The uploaded screenshots show that one account displayed a Google notice stating that the account was recently deleted and may be recoverable. Other Google recovery screenshots show that Google requested verification by phone number or recovery email, but I could not complete the recovery process with the information available to me were changed from the original Google account setup.
Because the domain, related website identity, two Google email accounts, and related security-camera evidence may no longer be within my reliable control, I consider the project identity, domain-related email accounts, and account records officially compromised from my standpoint pending provider review. I request preservation of all relevant IONOS, Google, GitHub, Ring, Wyze, Apple, device, network, billing, login, recovery, deletion, and camera-access records before any account closure, discontinuance, cancellation, recovery, account correction, domain change, or repository change occurs.
II. Background and Account Context
The domain name survivingthesystempodcast
The uploaded IONOS invoice / receipt shows the domain service associated with survivingthesystempodcast
On or about the same date, I created two Google email addresses to support the domain and project:
The email addresses were intended to be used for project communications, website support, future podcast activity, and account administration connected to the Surviving the System Podcast domain.
After the domain and website were created, I temporarily preserved the email account information on index cards. I intended to record the information into my permanent log book, but I did not immediately complete that step.
During the same general period, I relied on home security tools, including Ring and Wyze cameras, for personal safety, apartment monitoring, and incident documentation. Because I later suspected that the index cards were taken while I briefly left the apartment unit, **5, any interruption, disabling, pausing, or failure of Ring or Wyze camera evidence during that time is relevant to this report.
III. Careful Updated Theory of the Incident
Based on the facts presently available, the careful and evidence-supported theory is as follows:
- I established the IONOS domain survivingthesystempodca
st.com on or about November 21, 2025. - On or about that same date, I created two related Google email accounts:
- A GitHub website was later created for the domain.
- The Google account details were written on two index cards and placed on my desk.
- I did not immediately transfer those account details into my permanent log book.
- Between approximately December 15, 2025 and February 2026, I believe one or more unauthorized persons may have entered my Apartment Unit **5 while I briefly left to take out trash.
- I suspect the two index cards containing account credentials may have been taken from my desk during that unauthorized entry.
- I further suspect that the unauthorized person or persons may have used direct access to my Apple iPhone 17, or a mirrored / cloned access path connected to my Apple iPhone 17, to interfere with Ring and Wyze camera monitoring.
- The suspected camera interference may have included disabling cameras, interrupting recordings, pausing notifications, changing app/network access, preventing expected motion capture, or otherwise affecting evidence preservation.
- On May 25, 2026, I attempted to recover or access the related Google accounts.
- Google recovery screens showed that one account was recently deleted and may be recoverable.
- Google recovery also required phone or recovery-email verification that I could not successfully complete with the information available to me were unlawfully changed from the original recovery details.
- Because I cannot reliably access or verify control over the domain-related Google accounts, I consider the related account environment compromised pending provider review.
- I request that IONOS, Google, GitHub, Apple, Ring, Wyze, and any relevant internet / device / account service preserve records before any account closure, discontinuance, cancellation, recovery, transfer, reset, merge, or correction is performed.
I am not claiming technical certainty that my Apple iPhone 17 was mirrored or cloned. I am documenting that I suspect such access may have been used because of the circumstances, the missing account information, my inability to recover the related accounts, and my concern that Ring and Wyze camera evidence may have been affected during the suspected entry window.
IV. Incident Timeline
A. Domain Established Through IONOS
Date: November 21, 2025
Provider: IONOS
Domain: survivingthesystempodc
On or about November 21, 2025, I established the domain name survivingthesystempodcast
The uploaded IONOS invoice / receipt supports the existence of the domain purchase and service relationship. The invoice shows IONOS as the provider and identifies the domain service for survivingthesystempodcast.
This document is preserved as Exhibit A.
B. Google Email Accounts Created for the Domain
Date: On or about November 21, 2025
On or about the same date, I created two Google email accounts for the project:
These accounts were intended to support the new domain, website, and future podcast identity.
C. GitHub Website Created
After the domain was established, a GitHub-based website was created for:
The website was part of the project setup and was intended to support the public-facing podcast / project identity.
Because the website, domain, Google email accounts, and project identity were related, any compromise of the Google accounts may affect confidence in the domain and website identity.
D. Index Cards Containing Email Credentials Were Written and Left on Desk
After creating the Google email accounts, I wrote the two email addresses and related credential information on two index cards.
The index cards were placed on top of my desk in Apartment Unit **5. I intended to record the information into my permanent log book, but I was occupied with other web application work and did not complete that step immediately.
E. Suspected Unauthorized Physical Entry Into Apartment Unit **5
Approximate Date Range: December 15, 2025 through February 2026
Location: *****, ***** ******
I believe that sometime between approximately December 15, 2025 and February 2026, one or more unauthorized persons may have entered my apartment unit, **5 while I briefly left to take out trash.
When I later needed the two index cards, the credential information was no longer reliably available to me. Based on the circumstances, I believe the index cards may have been taken from the top of my desk.
I cannot identify the person or persons responsible from the current evidence. I am documenting this as a suspected unauthorized physical-entry and credential-compromise event.
F. Suspected Ring and Wyze Camera Interference
During the suspected unauthorized entry window, I am concerned that my Ring and Wyze cameras may have been disabled, paused, blocked, interrupted, or otherwise affected.
My current suspicion is that the unauthorized person or persons may have used one of the following methods:
- physical access to my Apple iPhone 17;
- mirrored or cloned access to my Apple iPhone 17;
- access to Ring or Wyze apps through an active phone session;
- app-level changes to camera settings or notifications;
- network-level interference affecting camera connectivity;
- account-level access affecting cloud recording or motion detection;
- temporary disabling of camera recording, camera status, or event alerts.
I do not yet have technical confirmation of the exact method. However, because Ring and Wyze cameras were relevant to apartment unit, **5 monitoring and evidence preservation, any lack of expected footage during the suspected entry window is an important part of this report.
I did not consent to any person accessing my Apple iPhone 17, mirroring my Apple iPhone 17, cloning my Apple iPhone 17, accessing Ring or Wyze camera applications, changing camera settings, disabling cameras, interrupting camera recording, or interfering with camera evidence.
G. Google Account Recovery Attempt for survivingthesystem@gmail.
Date: May 25, 2026
Evidence: Google “Account deleted” screenshot
On May 25, 2026, I attempted to access or recover the Google account:
The uploaded Google screenshot displayed the message:
“Account deleted”
“This account was recently deleted and may be recoverable. Click Next to attempt to restore this account.”
This screenshot is important because it indicates that the account may have been placed into a deleted or recoverable deleted-account state.
I did not knowingly intend for this account to be outside my control. Because this account was created for the domain-related project, the deleted-account notice increases my concern that the related account environment was compromised or no longer under my reliable access.
H. Google Account Recovery Attempt for survivingthesystempodcast@
Date: May 25, 2026
Evidence: Google recovery screenshots
On May 25, 2026, I also attempted to recover or access:
survivingthesystempodcast@
The uploaded Google recovery screenshots show that Google attempted to verify ownership by requesting a phone number or recovery email associated with the account.
The screenshots show recovery prompts requiring confirmation of information already associated with the account, including a partially masked phone number and a partially masked recovery email. When I entered available information, Google displayed an error indicating that the entered recovery email was incorrect.
Because I could not complete the recovery process, I remained unable to confirm full control over the account.
V. Evidence Summary
Exhibit A — IONOS Invoice / Receipt for survivingthesystempodcast.com
Description: IONOS invoice / receipt showing the domain service for survivingthesystempodcast.
Relevant Date: November 21, 2025.
Purpose: Confirms that the domain was established through IONOS and connected to a paid domain service.
Privacy note: The invoice contains personal address, customer ID, contract ID, invoice number, and billing details. These should be redacted before any public or general filing.
Exhibit B — Google “Account Deleted” Screenshot
Description: Google account screen for survivingthesystem@gmail.
“This account was recently deleted and may be recoverable.”
Purpose: Supports the fact that the account displayed a recently deleted / recoverable-account status during the May 25, 2026 account-access attempt.
Exhibit C — Google Account Recovery Phone Verification Screenshot
Description: Google recovery screen for survivingthesystempodcast@
Purpose: Supports that Google recognized the account as requiring ownership verification but did not allow immediate access with credentials available to me.
Exhibit D — Google Account Recovery Email Verification Screenshot
Description: Google recovery screen requesting confirmation of the recovery email address associated with the account.
Purpose: Supports that recovery required information I could not successfully complete during the May 25, 2026 recovery attempt.
Exhibit E — Google Recovery Error Screenshot
Description: Google recovery screen showing that an entered recovery email was marked incorrect.
Purpose: Supports that I was unable to regain access using the recovery information available to me.
Exhibit F — Later Google Phone Verification Prompt
Description: Google recovery screen requesting confirmation of the phone number associated with the account.
Purpose: Supports continuing inability to access the account without completing Google’s account-recovery verification process.
Exhibit G — Ring and Wyze Camera Review Needed
Description: The reporting party states that Ring and Wyze cameras were used for apartment monitoring and evidence preservation. The reporting party suspects the cameras may have been disabled, paused, interrupted, or made unavailable during the suspected unauthorized apartment-entry window.
Purpose: Supports a request for provider-side review of camera status, camera-event history, motion-detection history, cloud-recording logs, app-access logs, account-login logs, and device-session logs.
Exhibit H — Apple iPhone 17 Device Review Needed
Description: The reporting party suspects that the Apple iPhone 17 may have been directly accessed, mirrored, cloned, or otherwise used to interfere with Ring and Wyze camera functionality.
Purpose: Supports a request for technical review of Apple ID activity, device sessions, app access, screen activity, passcode / biometric access events if available, iCloud sessions, trusted devices, network activity, and related security records.
VI. Account-Security and Physical-Security Concerns
1. Credential Custody Concern
The two Google email accounts were created for the domain project, and the related credentials were written on index cards. Those index cards were later unavailable to me after a suspected unauthorized physical-entry event.
This creates a credential custody issue because the credentials may have been viewed, taken, copied, or used by someone without my consent.
2. Suspected Unauthorized Entry Concern
I believe one or more unauthorized persons may have entered my apartment unit, **5 while I briefly left to take out trash.
If this occurred, the entry was not authorized by me. I did not consent to anyone entering my apartment unit, **5, accessing my desk, taking index cards, viewing account information, using my devices, or interfering with camera systems.
3. Apple iPhone 17 Mirroring / Cloning Concern
I suspect that my Apple iPhone 17 may have been used as part of the incident either through direct physical access, mirrored access, cloned access, or other unauthorized access.
I cannot verify the technical method from the current evidence alone. However, because many security-camera applications can be managed through a phone app, unauthorized access to the phone or a phone session could create a pathway to camera interference.
This issue requires technical review rather than assumption.
4. Ring and Wyze Camera Interference Concern
The suspected interference with Ring and Wyze cameras is significant because camera footage could have been relevant to confirming whether an unauthorized person entered my apartment unit, **5.
If the cameras were disabled, paused, disconnected, prevented from recording, or otherwise affected, that would impair my ability to preserve evidence of the suspected entry.
I request preservation and review of Ring and Wyze records showing:
- camera online / offline status;
- motion-event history;
- recording history;
- device-health history;
- app login history;
- account-change history;
- notification settings;
- device sharing or user permissions;
- network connectivity records;
- camera power or disconnection events;
- deleted or missing event records, if available.
5. Google Account Access Concern
The Google recovery screenshots show that I could not regain access using the recovery process available to me.
The recovery flow required confirmation through information that I could not successfully complete, creating a practical lockout from the accounts.
6. Recently Deleted Google Account Concern
The screenshot showing that survivingthesystem@gmail.
I request preservation of any available account activity showing when the account was created, accessed, modified, placed into deleted status, recovered, or otherwise changed.
7. Domain Identity Concern
The domain survivingthesystempodca
For that reason, I consider the domain, related project identity, and related email accounts compromised from my standpoint unless provider records confirm otherwise.
8. GitHub Website Concern
A GitHub website was created after the domain was established. If the Google email accounts were used for setup, account administration, GitHub identity, recovery, or related project access, the website and repository access should also be reviewed.
I request that any related GitHub records, repository records, Pages configuration, DNS configuration, account linkage, and project-publication history be preserved before any changes are made.
VII. Impact on Reporting Party
This incident affected my ability to verify control over a domain-related project identity that I created and paid for.
The incident caused distress because the domain, website, and email accounts were established for my project, yet I could not access the related Google accounts through the standard recovery process.
The incident also caused concern that handwritten credentials may have been physically taken from my apartment unit, **5 desk and used, altered, or made unavailable without my consent.
The Ring and Wyze camera concern increases the severity of the incident because camera evidence may have been relevant to confirming whether unauthorized entry occurred. If camera systems were interrupted or disabled, that may have affected my ability to preserve evidence and protect my safety.
Because I cannot verify control over the related accounts, and because I suspect that account credentials and security-camera systems may have been affected, I no longer consider the domain and related Google email addresses safe for continued business, public-facing, or project use.
VIII. Legal Significance and Potentially Relevant Frameworks
This section is not a final legal conclusion. It identifies legal frameworks that may become relevant if later provider logs, device records, camera logs, forensic review, or law-enforcement review confirm unauthorized entry, account access, device misuse, interception, or account-data interference.
1. ***** ****** State Criminal Trespass / Dwelling Entry Review
***** ****** State law includes criminal-trespass provisions addressing unlawful presence in a residential dwelling or other protected property. If an unauthorized person entered Apartment Unit **5 without consent, this framework may be relevant for legal review.
2. Computer Fraud and Abuse Act — 18 U.S.C. § 1030
The Computer Fraud and Abuse Act addresses certain unauthorized-access activity involving protected computers and computer systems. If later evidence shows unauthorized access to my Apple iPhone 17, Google accounts, IONOS account, GitHub account, Ring account, Wyze account, or related platform records, this framework may become relevant. (U.S. Code)
3. Stored Communications Act — 18 U.S.C. § 2701
The Stored Communications Act addresses unauthorized access to facilities through which electronic communication services are provided where the conduct obtains, alters, or prevents authorized access to electronic communications in electronic storage. If later evidence shows unauthorized access to Google account records, email contents, stored recovery data, account messages, Ring / Wyze cloud records, or related stored communications, this statute may be relevant. (Legal Information Institute)
4. Wiretap Act / Interception of Communications — 18 U.S.C. § 2511
Federal law prohibits certain unauthorized interception, disclosure, or use of wire, oral, or electronic communications. If later evidence shows that electronic communications, camera feeds, app sessions, device sessions, or account communications were intercepted or used without authorization, this framework may be relevant for legal review. (Legal Information Institute)
5. Account, Device, and Evidence Preservation Significance
If a person entered my apartment unit, **5 without consent, took written credentials, accessed accounts, used my Apple iPhone 17, or interfered with Ring / Wyze camera monitoring, the conduct could affect both digital-account security and physical evidence preservation. This report is therefore intended to preserve the timeline, identify affected accounts and devices, and request technical review before any related account, domain, camera, or repository record is changed.
IX. Requested Corrective Action
A. For IONOS
I request that IONOS:
- Preserve all domain-registration and billing records for survivingthesystempodcast.
com. - Preserve account-access logs, login history, billing-change records, DNS-change records, and domain-management records.
- Confirm whether any changes were made to the domain account, DNS records, contact information, billing profile, or domain settings.
- Confirm whether anyone other than me accessed or attempted to modify the IONOS account.
- Prevent unauthorized transfer or change of the domain while the issue is reviewed.
- After evidence is preserved, assist with formally closing, discontinuing, or canceling the domain service if I choose to proceed.
B. For Google
I request that Google:
- Preserve account creation records for:
- Preserve login history, recovery attempts, deletion records, phone-number records, recovery-email records, device records, and account-change records.
- Confirm when survivingthesystem@gmail.
com entered the recently deleted / recoverable state. - Confirm whether either account was accessed, changed, deleted, or recovered from devices, IP addresses, or locations not associated with me.
- Confirm whether recovery phone numbers or recovery emails were changed after account creation.
- Provide a secure recovery path if Google can verify that I am the original account creator.
- If recovery cannot be completed safely, preserve the records and prevent further unauthorized use of the accounts.
C. For GitHub
I request that GitHub:
- Preserve any repository, Pages, DNS, deployment, commit, and account-linking records connected to survivingthesystempodcast.
com. - Confirm whether any GitHub account or repository connected to the website was accessed or changed by anyone other than me.
- Preserve any evidence of website creation, publishing, DNS configuration, and repository ownership.
- Preserve commit history and deployment history connected to the project website.
D. For Ring
I request that Ring:
- Preserve camera event records for the suspected date range.
- Preserve device online / offline records.
- Preserve motion detection records.
- Preserve account login records.
- Preserve device-sharing and permission records.
- Preserve app-access records where available.
- Preserve records of any camera disablement, recording interruption, deleted events, subscription status changes, or settings changes.
- Confirm whether camera access, recording, or notifications were changed from any device or session not associated with me.
E. For Wyze
I request that Wyze:
- Preserve camera event records for the suspected date range.
- Preserve device online / offline records.
- Preserve motion detection records.
- Preserve account login records.
- Preserve shared-user and permission records.
- Preserve camera settings and notification-setting records.
- Preserve any records of camera disablement, recording interruption, deleted events, or app-level changes.
- Confirm whether camera access, recording, or notifications were changed from any device or session not associated with me.
F. For Apple
I request that Apple preserve and provide, through proper lawful or account-recovery channels where available:
- Apple ID trusted-device records.
- Apple ID login records.
- iCloud session records.
- Device-session records for my Apple iPhone 17.
- Records of new trusted devices or browser sessions.
- Records of password, passcode, recovery, or account-security changes.
- Any records showing unusual access to apps, iCloud, or device sessions.
- Any available data relevant to determining whether my Apple iPhone 17 was mirrored, cloned, accessed, or used to alter Ring / Wyze camera access.
G. Personal Corrective Action
From my standpoint, I consider the following compromised pending provider review:
- The domain survivingthesystempodca
st.com. - The email account survivingthesystempodc
ast@gmail.com. - The email account survivingthesystem@
gmail.com. - Any GitHub website or repository configuration dependent on those accounts.
- Any Ring or Wyze camera evidence from the suspected entry window that cannot be independently verified.
- Any Apple iPhone 17 session, app access, or account setting that may have been used without my consent.
I request that all related accounts and services be closed, discontinued, or canceled only after relevant records are preserved.
X. Evidence Preservation Request
I request preservation of the following records:
- IONOS account records.
- IONOS domain purchase records.
- IONOS invoice and billing records.
- IONOS DNS records and domain-management logs.
- Google account creation records.
- Google login records.
- Google recovery attempt records.
- Google account deletion and restore records.
- Google recovery phone and recovery email change records.
- Google device and session records.
- GitHub repository records.
- GitHub Pages deployment records.
- DNS and website-publication records for survivingthesystempodcast.com.
- Ring camera event records.
- Ring camera online / offline history.
- Ring account login and app-session records.
- Wyze camera event records.
- Wyze camera online / offline history.
- Wyze account login and app-session records.
- Apple ID trusted-device and login records.
- Apple iPhone 17 device-session and security records.
- Network-router or Wi-Fi logs, if available.
- Any account-access, recovery, deletion, camera-status, camera-settings, or account-change records connected to the project identity.
- Any evidence showing whether an unauthorized person accessed, used, changed, deleted, or attempted to recover either Google account.
- Any evidence showing whether Ring or Wyze camera systems were disabled, paused, disconnected, or prevented from recording during the suspected entry window.
XI. Privacy and Redaction Notice
Before this report or the exhibits are submitted outside a secure support, legal, regulatory, or investigative channel, the following information should be redacted:
- Full residential address.
- Customer ID.
- Contract ID.
- Invoice number, unless needed for secure provider verification.
- Full phone numbers.
- Recovery phone number details.
- Recovery email details.
- Full Google account-recovery URLs.
- Browser address-bar tokens, challenge strings, or recovery parameters.
- Any unrelated browser tabs or personal desktop information.
- Any Apple ID session tokens or trusted-device identifiers.
- Any Ring / Wyze account identifiers not needed for provider review.
- Any Wi-Fi or router identifiers not needed for provider review.
The domain name and project-related email addresses may remain visible because they are central to the incident report.
XII. Formal Statement
I, Sarai Hannah Ajai, state that on or about November 21, 2025, I established the domain survivingthesystempodca
After establishing the domain and related website, I wrote the account information on two index cards and placed them on top of my desk. I intended to record the information in my permanent log book, but I did not complete that step immediately because I was occupied with other web application work.
I believe that sometime between approximately December 15, 2025 and February 2026, one or more unauthorized persons may have entered my apartment unit, **5 while I briefly left to take out trash and may have taken the index cards containing the account information. I cannot identify the person or persons responsible from the evidence presently available.
I further suspect that the unauthorized person or persons may have used my Apple iPhone 17, or a mirrored / cloned connection to my Apple iPhone 17, to interfere with my Ring and Wyze camera systems during or around the suspected entry. I did not consent to anyone accessing my Apple iPhone 17, using a mirrored or cloned device connection, opening camera apps, changing camera settings, disabling cameras, interrupting camera recording, or interfering with Ring / Wyze evidence.
On May 25, 2026, I attempted to recover the related Google accounts through Google’s account-recovery process. The uploaded screenshots show that survivingthesystem@gmail.
Because I cannot reliably access or verify control over these Google accounts, and because those accounts were connected to the domain identity and website project, I consider the domain-related account environment compromised from my standpoint pending provider review.
I request preservation of all relevant IONOS, Google, GitHub, Ring, Wyze, Apple, DNS, billing, login, recovery, deletion, camera, device, and account-change records. After preservation, I request formal closure, discontinuance, or cancellation of the compromised project accounts and domain services as appropriate.
Respectfully submitted,
Sarai Hannah Ajai
Date: May 25, 2026
Location: *****, ***** ******
Addendum — IONOS Domain Cancellation Confirmed
On May 25, 2026, I confirmed that the domain name survivingthesystempodcast
This cancellation was completed because I no longer considered the domain-related account environment secure due to suspected credential compromise involving the related Google email accounts:
The IONOS domain cancellation reduces the risk of future unauthorized use of the domain name, DNS records, website identity, or related project branding. However, this cancellation does not resolve the separate Google account-access concerns. I continue to consider the two related Google email accounts compromised unless Google later confirms recovery, closure, or permanent disabling.
Next steps
Save the IONOS cancellation confirmation, including any email, screenshot, ticket number, cancellation date, contract number, and domain name. Also confirm that auto-renewal is off, the domain is no longer attached to active hosting/DNS services, and no transfer authorization remains active.
For your evidence list, label the cancellation proof as:
Exhibit I — IONOS Cancellation Confirmation for survivingthesystempodcast.com
Comments
Post a Comment