Planet Starship Music

About Planet Starship Music

Founded in 2024, Planet Starship Music is a creative studio exploring the intersection of art, technology, and emotion.

Our mission is to craft experiences that transcend boundaries — where visuals pulse with rhythm and sound paints the universe.

Every beat, every glow, every motion tells a story of cosmic connection.

HEAD: empty BODY END: empty Clarity: not installed Publish: not performed 1. Verify Cookiebot Domain Group domains. 2. Confirm whether purple-music-253883.framer.app and/or planetstarshipmusic.io are included. 3. Save Cookiebot as the first script in Head if no duplicate exists. 4. Leave Body End empty until the Clarity integration is finalized. 5. Do not publish until testing and verification are complete. Cookiebot Script: Available Cookiebot Domain Group ID: 1d58a043-06c9-4f9c-8c34-ec5ba72fb31e Blocking Mode: Auto HEAD: reported empty BODY END: reported empty Installation: unverified Published: no Clarity: not installed Homepage B: unpublished data-blockingmode="auto" Cookiebot Domain Group ID: 1d58a043-06c9-4f9c-8c34-ec5ba72fb31e Generated Script: Present data-blockingmode: auto Auto Blocking Requested: YES Auto Blocking Active on Live Site: UNVERIFIED Installation: UNVERIFIED Publish Status: NOT VERIFIED No new clarity.ms script requests [ ] Banner appears [ ] Reject works [ ] Accept works [ ] Withdrawal works [ ] Re-consent works [ ] Returning visitor works [ ] No duplicate Clarity loads [ ] No console errors [ ] Cookiebot Verify passes HEAD: reported empty BODY END: intentionally empty Cookiebot: not installed (unverified) Clarity: not installed Homepage B: unpublished Production deployment: not performed Homepage B: Unpublished Cookiebot: Domain Group ID obtained Installation unverified Clarity: Not installed Framer: HEAD reported empty BODY END intentionally empty Financing Terms: Proposed / Subject to Verification ($1.8M raise, 15% equity, $10.2M pre-money, $12.0M post-money) Homepage B: Unpublished Cookiebot: ✓ Domain Group ID obtained □ Installation verified □ Domain configuration verified Clarity: □ Not installed □ Not validated Framer: HEAD reported empty BODY END intentionally empty Financing Terms: Proposed / Subject to Verification ($1.8M raise | 15% equity | $10.2M pre-money | $12.0M post-money) Homepage B: Unpublished Cookiebot: ✓ Domain Group ID obtained □ Installation verified □ Domain configuration verified Clarity: □ Not installed □ Not validated Framer: HEAD reported empty BODY END intentionally empty Financing Terms: Proposed / Subject to Verification ($1.8M raise | 15% equity | $10.2M pre-money | $12.0M post-money) Homepage B: Unpublished Cookiebot: ✓ Domain Group ID obtained □ Installation verified □ Domain configuration verified Clarity: □ Not installed □ Not validated Framer: HEAD reported empty BODY END intentionally empty Financing Terms: Proposed / Subject to Verification ($1.8M raise | 15% equity | $10.2M AUTOMATIC NO-GO CONDITIONS • Consent Withdrawal Test fails • Re-Consent Test fails • Cookiebot verification fails • Critical analytics conflict detected • Duplicate Cookiebot installation detected • Clarity loads before consent Homepage B: Unpublished Cookiebot: ✓ Domain Group ID obtained □ Domain configuration verified □ Installation verified □ Verification completed Clarity: □ Not installed □ Not validated Framer: HEAD reported empty BODY END intentionally empty Financing Terms: Proposed / Subject to Verification ($1.8M raise | 15% equity | $10.2M pre-money | $12.0M post-money) Any CRITICAL finding results in an automatic NO-GO. Two or more HIGH findings require technical review and documented approval before deployment. MEDIUM findings must be documented in the Defects & Remediation section. LOW findings may be deferred without affecting deployment status. Exceptions may be granted only for LOW or MEDIUM findings. HIGH findings require documented business justification, compensating controls, and executive approval. CRITICAL findings are not eligible for exception approval and automatically result in a NO-GO OPEN ↓ APPROVED ↓ REMEDIATION IN PROGRESS ↓ VALIDATION TESTING ↓ CLOSURE REVIEW ↓ CLOSED An exception cannot be marked CLOSED until: • All approved remediation actions are completed • Required validation tests pass • Evidence has been archived • Technical verification is completed • Business approval is recorded If remediation fails, the exception must either: 1. Be extended with approval, or 2. Be replaced by a new exception request. Critical findings remain non-exceptionable and cannot enter the closure workflow. • Every approved exception must have a unique Exception ID. • Every active exception must appear in the register. • Closed exceptions remain in the register for audit history. • Overdue exceptions require escalation according to SLA. • Critical (S1) items may not be approved as exceptions. • Exception status must be reviewed at least monthly. • Closure dates must be documented and verifiable. • Superseded exceptions must reference the replacement Exception ID. Draft Pending Review Approved Approved with Conditions Open Extended Closed Rejected Superseded Target Open Exceptions: < 10 Target Overdue Exceptions: 0 Target Closure Rate: > 90% Target Evidence Coverage: 100% Target Scheduled Reviews Completed: 100% Target Audit Trail Completeness: 100% Current Status Homepage B: Unpublished Cookiebot: ✓ Domain Group ID obtained □ Domain configuration verified □ Installation verified □ Verification completed Clarity: □ Installed □ Validated □ Withdrawal Tested □ Re-Consent Tested Framer: HEAD reviewed BODY END reviewed Financing Terms: Proposed / Subject to Verification ($1.8M raise | 15% equity | $10.2M pre-money | $12.0M post-money) 1. Screenshot(s) showing the actual code contents OR 2. Copy/paste all custom code blocks OR 3. Export the Framer project code settings Accept cookies ↓ Clarity loads Withdraw consent ↓ Clarity stops ↓ Clarity cookies removed ↓ Tracking ceases ` KEEP ✓ Required REMOVE ✗ Duplicate ✗ Obsolete REPLACE → Better implementation VERIFY ? Needs testing Code Register Duplicate Register Cookiebot Review Clarity Review Security Findings Remediation Checklist Final Approved Script Inventory Current Status: PAUSED – Pending Cookiebot Domain Verification • Cookiebot Domain Group ID: received and recorded. • No need to resend existing status information. • Next Action: provide the actual Cookiebot domain list for verification. • Site Changes: none. • Publishing Status: blocked pending verification and approval. No modifications will be made and no publication activity will occur until the configured Cookiebot domains have been reviewed and validated. www CNAME cname.vercel-dns.com planetstarshipmusic.io www.planetstarshipmusic.io staging.example.com planetstarshipmusic.io www.planetstarshipmusic.io A CNAME NS TXT • www CNAME points somewhere other than Framer • Missing apex/root A record • Old Webflow/Wix/Squarespace records still present • DNS changes have not propagated • Domain added incorrectly in Framer Type Host Value A AAAA CNAME TXT NS CAA Framer → Settings → Domains → planetstarshipmusic.io Registrar → DNS Management Type Host Value A @ 76.76.xxx.xxx CNAME www example.com TXT @ ... NS @ ... `` MX Name: @ Status: OK Value: 0 planetstarshipmusic-io.mail.protection.outlook.com TXT Name: @ Status: OK Value: v=spf1 include:spf.protection.outlook.com ... CNAME Name: autodiscover Status: OK Value: autodiscover.outlook.com NS Name: @ Value: ns1.bdm.microsoftonline.com NS Name: @ Value: ns2.bdm.microsoftonline.com NS Name: @ Value: ns3.bdm.microsoftonline.com NS Name: @ Value: ns4.bdm.microsoftonline.com A Records AAAA Records CNAME Records TXT Records (all custom entries) @ www mail (Microsoft 365): PASS ✅ Nameservers: PASS ✅ Framer website configuration: NOT VISIBLE ⚠️ Cause of Framer "Invalid DNS": cannot yet be determined A @ 31.43.160.6 A @ 31.43.161.6 CNAME www sites.framer.app MX ✅ Email TXT (PF) ✅ Email CNAME autodiscover ✅ Email NS ✅ Microsoft nameservers Visible website records: MX ✅ Email TXT (PF) ✅ Email CNAME autodiscover ✅ Email NS ✅ Microsoft nameservers Visible website records: A record for @ ❌ Not shown A record for @ ❌ Not shown CNAME for www ❌ Not shown 1. The required Framer A records have not been added. 2. The www CNAME has not been added. 3. Old website hosting records still exist. 4. DNS is being edited in the wrong place. 5. Propagation is incomplete. 1. The required Framer A records have not been added. 2. The www CNAME has not been added. 3. Old website hosting records still exist. 4. DNS is being edited in the wrong place. 5. Propagation is incomplete. Microsoft 365 Admin Center → Domains → planetstarshipmuic.io → DNS Records A AAAA CNAME (especially www) TXT (verification) Plain Text Framer → Settings → Domains → planetstarshipmusic.io Framer → Settings → Domains Required DNS Records Type Name Value A @ ... A @ ... CNAME www ... Required DNS Records Type Name Value A @ ... A @ ... CNAME www ... MX planetstarshipmusic-io.mail.protection.outlook.com TXT v=spf1 include:spf.protection.outlook.com ... CNAME autodiscover.outlook.com NS ns1-4.bdm.microsoftonline.com MX planetstarshipmusic-io.mail.protection.outlook.com TXT v=spf1 include:spf.protection.outlook.com ... CNAME autodiscover.outlook.com NS ns1-4.bdm.microsoftonline.com Framer → Settings → Domains → planetstarshipmusic.io Required DNS Records GTM-PK7MFGVV Not sure how to do it? See an example © 2026 Microsoft LegalPrivacy & CookiesAdvertiseDevelopersSupportBlogCommunityConsumer Health Privacy How to fix Ensure a Reject All button is visible on your banner. Configuration > Compliance > set Type to that contains "Reject all" > save Switch to explicit consent collection. Configuration > Compliance > set Method to Explicit Consent > save