§ 1

Verification Duties

1.1 The NIS2 Directive (EU) 2022/2555 is a directive and does not bind undertakings directly; what applies is its transposition into German law. As a provider of domain name registration services within the meaning of § 2 No. 9 BSIG, we are required by § 49 BSIG to maintain a database of accurate and complete registration data and to have procedures in place to verify it. The procedures described below serve to discharge that duty; the statute does not prescribe a particular verification method.

1.2 We verify the email address and the telephone number of the domain holder (registrant contact). We carry out a new registration only once both details are confirmed; without complete verification no domain is registered.

1.3 The verification requirement applies to natural persons as well as legal entities and organisations. For legal entities, the email address and telephone number of the named contact person held in the registrant contact are verified.

§ 2

Verification Process

2.1 Email verification is performed with a confirmation code that we send to the email address stored in the contact. The code is valid for 15 minutes, or for seven days in the case of the annual confirmation under § 3.4, and is entered in the customer portal.

2.2 Telephone verification is performed by:

  • a confirmation code sent by SMS to the mobile number held in the contact; the code is valid for 10 minutes and is entered in the customer portal

2.3 At most five attempts are possible per code; after expiry or use a new code can be requested. The number of codes per email address and per telephone number is limited per hour. Landline numbers cannot be verified by SMS; in that case, provide a mobile number. A voice call is not offered.

2.4 If the same email address or telephone number is already verified on another contact of the same customer account, we carry the verification over without a new code. Successful verification is displayed in the customer account and documented with a timestamp.

§ 3

Deadlines and Revalidation

3.1 For newly created domain contacts the verification period is 30 days from creation. A new registration is possible only after complete verification (§ 1.2).

3.2 If the email address or telephone number of a contact is changed, the verification of the changed detail lapses. Re-verification must be completed within 30 days of the change.

3.3 For domains imported to us, the verification period is 90 days from import. We send email reminders after 30, 60 and 80 days.

3.4 We reconfirm the email address of every contact annually. Once a year has passed since the last confirmation, we send a request with a confirmation code to the address on file; the code is valid for seven days, and a new code can be requested in the customer portal at any time. We also send the first request of a year to the email address of the customer account, unless it is the same as the address on file. If confirmation is not completed, we send a reminder every 30 days. The deadline for confirmation is 60 days from the day on which we send the first request of the respective year; later reminders do not extend it. If confirmation is not completed within the deadline, the email address is treated as unverified and must be verified again within 30 days. Each confirmation restarts the year. In addition, we reserve the right to request re-verification in justified cases, in particular where there is suspicion of incorrect data or complaints from third parties.

§ 4

Consequences of Non-Compliance

4.1 No new domains can be registered with a contact whose verification is outstanding or whose deadline has expired.

4.2 If verification of a contact remains outstanding after the deadline, we may suspend the affected domains; we inform the customer by email. A suspended domain no longer resolves and is not reachable on the internet.

4.3 A suspension for missing verification is lifted as soon as verification is completed. Regular domain fees continue to apply during suspension.

4.4 If verification remains outstanding for more than 60 days after the deadline, we may terminate the domain contract for good cause and release the domain at the registry (§ 6.6 of the Domains service agreement). A released domain cannot be restored by us.

Part 2: Disclosure of Registration Data

§ 5

Authorised Requesters

5.1 Under § 50 BSIG we grant legitimate access seekers access to domain registration data upon reasoned request. Legitimate access seekers are, exhaustively per § 2 No. 2 BSIG, the Federal Office for Information Security, the Land authorities, the prosecuting authorities, the federal and Land police forces and the constitutional protection authorities. Beyond that we handle, voluntarily and with no statutory obligation, requests from the following bodies after case-by-case review:

  • Law enforcement authorities (LEA) in the course of ongoing investigations
  • Computer Emergency Response Teams (CERT/CSIRT) in case of security incidents
  • Intellectual property enforcement authorities (IP Enforcement)
  • Courts and court-appointed executors
  • Other authorities with a legal basis

5.2 Private lawyers or companies are not directly entitled to request information, but may obtain information through competent authorities or in the course of court proceedings.

§ 6

Request Process

6.1 Requests must be submitted in writing to: disclosure@itsh.dev

6.2 The request must contain the following information:

  • Name, organisation and contact details of the requester
  • Proof of authorisation (e.g. official ID, court order)
  • File reference or case number
  • Affected domain(s)
  • Legal basis for the request
  • Specific data required and justification

6.3 Incomplete requests will be rejected with reference to missing information.

§ 7

Decision Criteria

7.1 Each request is assessed according to the following criteria:

  • Legitimacy: Is the requester authorised pursuant to section 5?
  • Legal basis: Is there a valid legal basis?
  • Proportionality: Is the requested data necessary for the purpose?
  • Data minimisation: Is only necessary data being requested?

7.2 If there are doubts about the authorisation, a query may be made to the requester or the superior authority.

7.3 Refusals are given with reasons in text form. A requester may lodge a complaint against a refusal with the competent data protection supervisory authority; for us this is the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia (LDI NRW), Kavalleriestr. 2-4, 40213 Düsseldorf, Germany.

§ 8

Processing Deadlines

8.1 We answer requests from legitimate access seekers under § 50 BSIG without undue delay and in any event within 72 hours of receipt. Where the requested data is not available, we say so within 24 hours. In detail:

  • Law enforcement authorities (LEA): 72 hours
  • CERT/CSIRT for active security incidents: 72 hours
  • Court orders: 72 hours
  • Voluntarily handled requests (not § 2 No. 2 BSIG): 7 business days

8.2 For urgent requests (imminent danger), we endeavour to process them more quickly. Please mark such requests accordingly.

8.3 Deadlines begin upon receipt of a complete request pursuant to section 6.2.

§ 9

Disclosed Data

9.1 The following data may be disclosed upon authorised request:

  • Name of the domain holder (natural or legal person)
  • Address of the domain holder
  • Email address of the domain holder
  • Telephone number of the domain holder
  • Registration and expiry date of the domain
  • Technical contact details (if different)

The following data will not be disclosed:

  • Passwords or access credentials
  • Payment information (credit cards, bank details)
  • Internal customer numbers or account IDs
  • Communication history with customer support

9.3 A court order is required for further data.

Part 3: Abuse Handling

§ 10

Reporting Process

10.1 Abuse reports can be submitted through the following channels:

  • Online form via the "Report Abuse" link in the footer
  • Email to: abuse@itsh.dev

10.2 A report should contain the following information:

  • Affected domain(s)
  • Type of abuse (see section 11)
  • Description of the incident with evidence (screenshots, URLs, etc.)
  • Contact details of the reporter (email required)

10.3 Anonymous reports will be processed, but no feedback can be provided without contact details.

§ 11

Categories

11.1 We process abuse reports in the following categories:

  • Spam: Unsolicited mass emails or advertising via the domain
  • Phishing: Deceptive websites for obtaining credentials
  • Malware: Distribution of malicious software via the domain
  • Incorrect registration data: Obviously false holder information
  • Trademark infringement: Infringement of registered trademarks
  • Other: Other violations of our terms of service

11.2 For criminally relevant content (e.g. child abuse), a report is immediately made to the competent authorities.

§ 12

Processing Workflow

12.1 After receipt of a report, processing takes place in the following steps:

1. Acknowledgement of receipt

The reporter receives an automatic confirmation with a case number.

2. Review

Our team reviews the report for completeness and plausibility.

3. Investigation

For legitimate reports, the domain holder is contacted and asked to respond.

4. Decision

Based on the results, a decision is made on measures.

5. Closure

The reporter is informed of the outcome (where contact details are available).

12.2 We aim for a maximum processing time of 7 business days. Complex cases may take longer.

§ 13

Domain Suspension

13.1 A domain may be suspended in the following cases:

  • Confirmed abuse pursuant to section 11
  • Non-compliance with verification requirements pursuant to section 4
  • Court order or official decree
  • Serious violations of the Terms and Conditions

13.2 Upon suspension, the domain holder is notified by email. The domain is not reachable on the internet during suspension.

13.3 The domain holder may lodge an objection within 14 days. The objection must be submitted in writing with reasons to support@itsh.dev.

13.4 In case of a justified objection, the suspension will be reviewed. The decision on the objection will be made within 7 business days.

13.5 In case of permanent suspension without successful objection, the domain may be deleted after 60 days.