Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add seidat.net private domain #974

Merged
merged 1 commit into from
May 22, 2020
Merged

Add seidat.net private domain #974

merged 1 commit into from
May 22, 2020

Conversation

anschutz
Copy link
Contributor

@anschutz anschutz commented Feb 19, 2020

  • Description of Organization
  • Reason for PSL Inclusion
  • DNS verification via dig
  • Run Syntax Checker (make test)

Description of Organization

Organization Website: https://www.seidat.com

Seidat is a cloud presentation platform for teams. I am responsible for the technology and infrastructure there.

Reason for PSL Inclusion

We'd like to let our customers run their own Google Tag Manger containers in a sandboxed iframe (hosted on seidat.net) for presentation analytics. Letting them run their GTM setup effectively means allowing them to execute any code in the iframe. Each team loads the iframe from its own subdomain (example: team_id.seidat.net). We'd like to restrict the ability to set cookies on the parent domain to isolate teams from one another.

DNS Verification via dig

dig +short TXT _psl.seidat.net
"https://github.com/publicsuffix/list/pull/974"

make test

Passed

@dnsguru
Copy link
Member

dnsguru commented May 22, 2020

Is this for an internal-use-only project?

@dnsguru
Copy link
Member

dnsguru commented May 22, 2020

@anschutz can you clarify the request? Is this an internal-only namespace being requested?

@dnsguru dnsguru added the waiting-followup Blocked for need of follow-up label May 22, 2020
@dnsguru dnsguru self-assigned this May 22, 2020
@anschutz
Copy link
Contributor Author

This domain will be used by our customers. We let them run their Google Tag Manager containers on this domain in an iframe that's baked into our production web app (https://app.seidat.com). So this is not for internal use. We have no control of what code our customers run in their Tag Manager containers.

@anschutz
Copy link
Contributor Author

Adding to that, this is not for our customers' internal use either. This subdomain is used to run analytics of the slide decks our customers create using our app. Those slide decks are most of the time shared with anonymous visitors and are publicly available.

@dnsguru dnsguru removed the waiting-followup Blocked for need of follow-up label May 22, 2020
@dnsguru dnsguru self-requested a review May 22, 2020 09:09
Copy link
Member

@dnsguru dnsguru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • DNS Validates
  • Rationale Sufficient (with clarifications from submitter, ok)
  • Tests ok
  • No conflict with base

Approved

@dnsguru dnsguru merged commit 565129e into publicsuffix:master May 22, 2020
@dnsguru
Copy link
Member

dnsguru commented May 22, 2020

@anschutz thank you for the clarifications; approved and merging.

@dnsguru dnsguru mentioned this pull request Aug 3, 2020
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants