DNS Tool

Engineer's DNS Intelligence Report

Generated 7 Mar 2026, 23:32 UTC
Duration 23.4s
Version v26.35.15
Integrity 71d3e8daaa6fa6f1d5b8d436f39ae18df53a3c13314556c9850aeaf6854862dccd19d0061b83e81f737fc961bd46cdcb13e8a4341b208cc1a6a9403bfd34ed0d

TLP:AMBER

Limited disclosure — recipients may share within their organization only

Subject Domain

uke.de

Engineer's DNS Intelligence Report

uke.de

7 Mar 2026, 23:32 UTC · 23.4s ·v26.35.15 · SHA-3-512: 71d3✱✱✱✱ Verify

Executive Methodology

Recon Mode Snapshot Re-analyze New Domain

Footprint 1 SaaS Service

DNS Security & Trust Posture

Risk Level: Low Risk

4 protocols configured, 5 not configured Why we go beyond letter grades

1 recommendation 1 monitoring

Analysis Confidence (ICD 203)

MODERATE 68/100

Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.

Accuracy 65% Currency 72/100 Maturity verified

Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers

Intelligence Currency

Data Currency: Adequate 72/100

ICuAE Details

Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Degraded

DNS data shows some aging or gaps — consider re-scanning for critical decisions

The following DNS record TTLs deviate from recommended values. Incorrect TTLs can cause caching issues, slow propagation, or unnecessary DNS traffic.

Record Type	Observed TTL	Typical TTL	Severity	Context
TXT	`21570s`	`1 hour (3600s)`	high	TXT TTL is above typical — observed 21570s, typical value is 1 hour (3600s). Long TTLs reduce DNS query volume but slow propagation when records change. Consider 3600 seconds for a balance of performance and flexibility per NIST SP 800-53 SI-18 relevance guidance.
NS	`21569s`	`1 day (86400s)`	medium	NS TTL is below typical — observed 21569s, typical value is 1 day (86400s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 86400 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
CAA	`21569s`	`1 hour (3600s)`	high	CAA TTL is above typical — observed 21569s, typical value is 1 hour (3600s). Long TTLs reduce DNS query volume but slow propagation when records change. Consider 3600 seconds for a balance of performance and flexibility per NIST SP 800-53 SI-18 relevance guidance.
A	`6 hours (21600s)`	`1 hour (3600s)`	high	A TTL is above typical — observed 6 hours (21600s), typical value is 1 hour (3600s). Long TTLs reduce DNS query volume but slow propagation when records change. Consider 3600 seconds for a balance of performance and flexibility per NIST SP 800-53 SI-18 relevance guidance.
SOA	`6 hours (21600s)`	`1 hour (3600s)`	high	SOA TTL is above typical — observed 6 hours (21600s), typical value is 1 hour (3600s). Long TTLs reduce DNS query volume but slow propagation when records change. Consider 3600 seconds for a balance of performance and flexibility per NIST SP 800-53 SI-18 relevance guidance.

Big Picture Questions

How often do you actually change this record? If it hasn’t changed in months, a short TTL is generating unnecessary DNS queries without any benefit.
Are you preparing for a migration or IP change? Short TTLs make sense temporarily — but should be raised back to 1 hour (3600s) once the change is complete.
Every DNS lookup adds 20–150ms of latency. With a 60s TTL, returning visitors trigger a fresh lookup every minute. With 3600s, they get cached responses for an hour — faster page loads, no extra infrastructure needed.
Google runs A records at ~30s because they operate a global anycast network and need to steer traffic dynamically. For a typical website without that infrastructure, copying those TTLs increases query volume with zero upside.

Tune TTL for uke.de

Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) Note: Some DNS providers (e.g., AWS Route 53 alias records, Cloudflare proxied records) enforce fixed TTLs that cannot be modified. If a finding targets a record you cannot edit, it reflects the observed value rather than a configuration error on your part.

Primary NS netman.uke.uni-hamburg.de

Serial 2026022700

Admin net-security.uke.de

Provider Unknown

Timer	Value	RFC 1912 Range
Refresh	`10800s`	1,200–43,200s (20 min – 12 hrs)
Retry	`3600s`	Fraction of Refresh
Expire	`2419200s`	1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)	`7200s`	300–86,400s (5 min – 1 day)

All SOA timer values are within RFC 1912 recommended ranges.

Email Spoofing

Protected

Brand Impersonation

Not Setup

DNS Tampering

Unsigned

Certificate Control

Configured

Recommended

Add DMARC aggregate reporting (rua) for visibility into email authentication

Monitoring

DKIM signing inferred from provider — could not directly verify selector

Configured

SPF (hard fail), DMARC (reject), DKIM (inferred via Self-hosted), CAA

Not Configured

MTA-STS, TLS-RPT, BIMI, DANE, DNSSEC

Priority Actions 5 total Achievable posture: Secure

Medium Add DMARC Aggregate Reporting

Add a rua= tag to receive aggregate DMARC reports. Without reporting, you cannot monitor authentication failures.

Aggregate reports show who is sending mail as your domain and whether it passes authentication.

Field	Value
Type	`TXT`
Host	`_dmarc.uke.de` (add to existing DMARC record)
Value	`rua=mailto:dmarc-reports@uke.de`

RFC 7489 §7.1

Medium Enable DNSSEC

DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.

RFC 4035

Low Add BIMI Record

Your domain has DMARC reject — you qualify for BIMI, which displays your brand logo in receiving email clients that support it (Gmail, Apple Mail, Yahoo).

BIMI displays your verified brand logo next to your emails in supporting mail clients.

Field	Value
Type	`TXT`
Host	`default._bimi.uke.de` (BIMI default record)
Value	`v=BIMI1; l=https://uke.de/brand/logo.svg`

RFC 9495

Low Add TLS-RPT Reporting

TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain.

TLS-RPT sends you reports about TLS connection failures to your mail servers.

Field	Value
Type	`TXT`
Host	`_smtp._tls.uke.de` (SMTP TLS reporting record)
Value	`v=TLSRPTv1; rua=mailto:tls-reports@uke.de`

RFC 8460

Low Deploy MTA-STS

MTA-STS enforces TLS encryption for inbound mail delivery, preventing downgrade attacks on your mail transport.

MTA-STS tells sending servers to require TLS when delivering mail to your domain.

Field	Value
Type	`TXT`
Host	`_mta-sts.uke.de` (MTA-STS policy record)
Value	`v=STSv1; id=uke.de`

RFC 8461

Registrar (RDAP) LIVE

Unknown

Where domain was purchased

Email Service Provider INFERRED

Self-hosted

Strongly Protected

Web Hosting

Unknown

Where website is hosted

DNS Hosting

Unknown

Where DNS records are edited

Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

SPF Record RFC 7208 §4 Verified

Does this domain declare who may send email on its behalf? Yes

Success -all 4/10 lookups

SPF valid with strict enforcement (-all), 4/10 lookups

v=spf1 mx ip4:134.100.101.8/30 ip4:134.100.53.70 ip4:134.100.53.101 ip4:134.100.38.112/30 ip4:188.138.124.28 ip4:62.245.148.4 ip4:94.199.88.64/26 ip4:94.199.90.64/26 ip4:134.119.253.31 ip4:217.113.45.225 ip4:85.13.149.7 include:spf.qb-feedback.com include:spf.protection.outlook.com include:spf.embloom.com -all

RFC 7489: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked

RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.

RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.

Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)

SPF hard fail (-all): compliance-strong, but can short-circuit DMARC. RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
DMARC is set to reject — enforcement is strong. However, some receivers may still reject messages on SPF hard fail before DKIM alignment is checked. Switching to ~all + p=reject would provide the same enforcement with full DMARC compatibility.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Yes — reject policy

Success p=reject

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; adkim=r; aspf=r; ruf=mailto:dmarc-reports@uke.de

Alignment: SPF relaxed DKIM relaxed

No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing

No aggregate reporting (rua) configured — you won't receive reports about authentication results and potential abuse

Forensic reporting (ruf) is configured, but most major providers do not send forensic reports. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record. RFC 7489 §7.3 — Forensic Reports

RFC 7489 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.

DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.

Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Verified

Are outbound emails cryptographically signed? Provider-managed

Provider Verified

DKIM not discoverable via common selectors (large providers use rotating selectors)

Self-hosted detected as primary mail platform — DKIM signing is managed by the provider. The primary provider may use custom selectors not discoverable through standard checks.

Know your DKIM selector? Re-scan with a custom selector to verify.

SPF authorizes Microsoft 365 servers, but MX records point to self-hosted infrastructure. The Microsoft 365 SPF include likely supports ancillary services (e.g., calendar invitations, shared documents) rather than primary mailbox hosting.

RFC 6376 (Provider-Managed) — DKIM signing managed by the detected mail provider per RFC 6376.

Known Vulnerabilities: DKIM l= tag body length vulnerability (attacker appends unsigned content to signed mail), weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3), DKIM replay attacks (re-sending legitimately signed messages at scale)

MTA-STS RFC 8461 §3 Verified

Can attackers downgrade SMTP to intercept mail? Not prevented

Warning

No MTA-STS record found

MTA-STS policy enforcement is evaluated in Mail Transport Security below.

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? No reporting

Warning

No TLS-RPT record found

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No

RFC 7672 §3 RFC 6698 §2 Not Configured

No DANE/TLSA records found (checked 2 MX hosts)

DANE (RFC 7672) binds TLS certificates to DNSSEC-signed DNS records, protecting email transport against man-in-the-middle attacks and rogue CAs. It is the primary transport security standard — MTA-STS (RFC 8461) was created as the alternative for domains that cannot deploy DNSSEC. Over 1 million domains use DANE globally, including Microsoft Exchange Online, Proton Mail, and Fastmail. Best practice: deploy both for defense in depth.

Email Transport Security

Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:

DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).

This domain has neither DANE nor MTA-STS. Mail transport relies on opportunistic TLS without policy enforcement, leaving it vulnerable to downgrade attacks. Deploy DANE (RFC 7672) with DNSSEC for the strongest protection, or MTA-STS (RFC 8461) if DNSSEC is not feasible.

Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).

Brand Security Can this brand be convincingly faked? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity

BIMI BIMI Spec Verified Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Verified Success IODEF

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only harica.gr, Sectigo, pki.dfn.de can issue certificates (wildcard issuance: harica.gr per RFC 8659 §4.3)

Authorized CAs: harica.gr Sectigo pki.dfn.de

0 issue "harica.gr"

0 iodef "mailto:net-security@uke.de"

0 issuewild "harica.gr"

0 issue "sectigo.com"

0 issue "pki.dfn.de"

Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Partial RFC 9116

security.txt found but missing required fields

Contact

Missing (required by RFC 9116 §2.5.3)

Expires

Missing (required by RFC 9116 §2.5.5)

Source: https://uke.de/.well-known/security.txt

Missing required Contact field (RFC 9116 §2.5.3)

Missing required Expires field (RFC 9116 §2.5.5)

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? Yes

AI governance signals observed

llms.txt llmstxt.org

Is this domain publishing AI-readable brand context? Yes

llms.txt found — domain provides structured context for LLMs

llms-full.txt also found (extended LLM context)

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Are AI crawlers explicitly allowed or blocked? Not blocked

No AI crawler blocking observed — no blocking directives found in robots.txt

Content-Usage Directive IETF Draft

Does the site express AI content-usage preferences? Not Configured

No Content-Usage directive detected. The IETF AI Preferences working group is developing a Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.

Example: Add Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it. Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.

AI Recommendation Poisoning

Is this site trying to manipulate AI recommendations? No

No AI recommendation poisoning indicators found

Hidden Prompt Artifacts

Is hidden prompt-injection text present in the source? No

No hidden prompt-like artifacts detected

Evidence Log (3 items)

Type	Detail	Severity	Confidence
`llms_txt_found`	llms.txt file found providing structured LLM context	info	Observed
`llms_full_txt_found`	llms-full.txt also found (extended LLM context)	info	Observed
`robots_txt_no_ai_blocks`	robots.txt found but no AI-specific blocking directives	low	Observed

Public Exposure Checks Are sensitive files or secrets exposed? No

No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.

What type of scan is this?

This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.

Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.

Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.

DNS Server Security Hardened

No DNS server misconfigurations found on dns-3.dfn.de — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.

Check	Result	Detail
Zone Transfer (AXFR)	Denied	Zone transfer denied (correct configuration)
Open Recursion	Disabled	Recursion disabled (correct configuration)
Nameserver Identity	Hidden	No nameserver identity information disclosed
Cache Snooping	Protected	Cache snooping not possible (correct configuration)

Tested nameservers: dns-3.dfn.de, dns2.rrz.uni-hamburg.de, rzdspc1.informatik.uni-hamburg.de, netman.uke.uni-hamburg.de, dns1.rrz.uni-hamburg.de

Delegation Consistency 1 Issue

Delegation consistency: 1 issue(s) found — Parent/child NS delegation alignment: DS↔DNSKEY, glue records, TTL drift, SOA serial sync.

Findings:

Could not retrieve NS TTL from parent zone

DS ↔ DNSKEY Alignment Aligned

Glue Record Completeness Complete

Nameserver	In-Bailiwick	IPv4 Glue	IPv6 Glue	Status
`dns-3.dfn.de`	No	N/A	N/A	OK
`dns1.rrz.uni-hamburg.de`	No	N/A	N/A	OK
`dns2.rrz.uni-hamburg.de`	No	N/A	N/A	OK
`netman.uke.uni-hamburg.de`	No	N/A	N/A	OK
`rzdspc1.informatik.uni-hamburg.de`	No	N/A	N/A	OK

NS TTL Comparison Drift

Child TTL: 604800s Drift: 0s

SOA Serial Consistency Consistent

dns-3.dfn.de: 2.0260227e+09

dns1.rrz.uni-hamburg.de: 2.0260227e+09

dns2.rrz.uni-hamburg.de: 2.0260227e+09

netman.uke.uni-hamburg.de: 2.0260227e+09

rzdspc1.informatik.uni-hamburg.de: 2.0260227e+09

Nameserver Fleet Matrix Healthy

Analyzed 5 nameserver(s) for uke.de — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Nameserver	IPv4	IPv6	ASN / Operator	SOA Serial
`netman.uke.uni-hamburg.de`	134.100.103.99	None	AS680	2026022700
`dns2.rrz.uni-hamburg.de`	134.100.33.229	2001:638:710:21::532	AS680	2026022700
`dns-3.dfn.de`	193.174.75.58	2001:638:d:b103::1	AS680	2026022700
`rzdspc1.informatik.uni-hamburg.de`	134.100.9.61	None	AS680	2026022700
`dns1.rrz.uni-hamburg.de`	134.100.33.228	2001:638:710:21::531	AS680	2026022700

Unique ASNs

Unique Operators

Unique /24 Prefixes

Diversity Score

Fair

1 ASN(s), 4 /24 prefix(es) — consider adding diversity

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

All 2 server(s) verified: encrypted transport confirmed via direct SMTP probe and DNS policy

Policy Assessment Primary

No transport enforcement policies detected. Mail delivery relies on opportunistic STARTTLS, which is vulnerable to downgrade attacks (RFC 3207). Consider deploying MTA-STS (RFC 8461) or DANE (RFC 7672).

Telemetry

TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders

Live Probe Supplementary

MX Host	STARTTLS	TLS Version	Cipher	Certificate
`iplexus2.uke.uni-hamburg.de`		TLSv1.3	TLS_AES_256_GCM_SHA384	Valid Expires: 2026-09-29 (205 days) Issuer: Hellenic Academic and Research Institutions CA
`iplexus1.uke.uni-hamburg.de`		TLSv1.3	TLS_AES_256_GCM_SHA384	Valid Expires: 2026-09-29 (205 days) Issuer: Hellenic Academic and Research Institutions CA

Multi-Vantage Probe Results

Unanimous: TLS verified 2 probes, 1 responded

France - EU observed

All servers support TLS

US-East (Boston) skipped

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

Resolved 1 unique ASN(s) across 1 IP address(es)

ASN	Name	Country
`AS680`		DE

IPv4 Mappings:

134.100.186.245 → AS680 (134.100.0.0/16)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 1 service

1 SaaS service detected via DNS TXT verification records

Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.

Service	Verification Record
Apple	`apple-domain-verification=1GQjQjLP9HX5pIuQ`

Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

DNSSEC RFC 4033 §2 Verified Unsigned

DNSSEC not configured - DNS responses are unsigned

Domain does not use DNSSEC. Enable in your registrar's DNS settings (look for "DNSSEC" or "DS records" section).

NS Delegation Verified

5 nameserver(s) configured

Nameservers: dns-3.dfn.de dns1.rrz.uni-hamburg.de dns2.rrz.uni-hamburg.de netman.uke.uni-hamburg.de rzdspc1.informatik.uni-hamburg.de

Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (1 difference found)

Resolver Differences:

TXT: OpenDNS returned different results: [+Rb+uEdewC04f3D77kvCwB569XYEXvgy0RbBUMr0N1ArwAj7KV1+zJM9z4DKVu/FdmP3UgQbh349d2t1t46Mfw== HARICA-H5xiO7XVCKEPOQBDTcn HARICA-QhKCSJkzCNyflY5R9Pc HARICA-ZhBU9ncDgtZ7MBJWiPY apple-domain-verification=1GQjQjLP9HX5pIuQ brevo-code:28b9a7401bb622df5de67e49fa7f2dda brevo-code:543fecfd7af25c0498807d050d3c2553]

This may indicate DNS propagation in progress or geo-based DNS routing.

Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

134.100.186.245

Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records

IPv6 not configured

MXMail Servers

0 iplexus1.uke.uni-hamburg.de.

0 iplexus2.uke.uni-hamburg.de.

Priority + mail server for email delivery

Self-hosted

SRVServices

_sip._tls: 20 0 5061 srvkdxprwayep03.uke.de.

_sip._tls: 10 0 5061 srvewaye01.uke.de.

SIP, XMPP, or other service endpoints

Web: Reachable (1 IPv4, 0 IPv6) Mail: 2 servers Services: 2 endpoints

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 491 subdomains discovered

How did we find these?

CT logs unavailable 491 current 0 expired 10 CNAMEs Source: Certificate Transparency + DNS Intelligence

Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.

Subdomain	Source	Status	Provider / CNAME	Certificates	First Seen	Issuer(s)
`3eb37ab5954f53cb72be05ecad92bb26-entwicklung.uke.de`	CT Log	Current	—	1	2026-02-09T09:17:35Z
`3eb37ab5954f53cb72be05ecad92bb26-konsolidierung.uke.de`	CT Log	Current	—	1	2026-02-09T09:17:35Z
`3eb37ab5954f53cb72be05ecad92bb26.uke.de`	CT Log	Current	`srvw1prxav-reverse.uke.de`	1	2026-02-09T09:17:35Z
`aaa.uke.de`	CT Log	Current	—	1	2026-02-03T06:46:03Z
`acc-laborbuch.uke.de`	CT Log	Current	—	4	2025-07-17T12:06:16Z
`acc-occ-laborbuch.uke.de`	CT Log	Current	—	1	2025-10-08T09:13:47Z
`acc-oos-laborbuch.uke.de`	CT Log	Current	—	2	2025-07-17T12:06:16Z
`activesync.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`aida-admin.uke.de`	CT Log	Current	—	1	2025-10-16T13:19:31Z
`aida-dev.uke.de`	CT Log	Current	—	2	2025-10-16T13:19:31Z
`aida-maintenance.uke.de`	CT Log	Current	—	1	2025-10-30T17:04:02Z
`aida-test.uke.de`	CT Log	Current	—	1	2025-10-30T17:04:02Z
`aida.uke.de`	CT Log	Current	—	2	2025-10-16T13:19:31Z
`app.uke.de`	CT Log	Current	—	1	2025-12-09T07:56:40Z
`asms-test.uke.de`	CT Log	Current	—	1	2025-11-11T08:11:14Z
`asms.uke.de`	CT Log	Current	—	1	2025-11-11T08:11:14Z
`ausbildung.uke.de`	CT Log	Current	—	1	2026-01-20T09:02:41Z
`auth.uke.de`	CT Log	Current	—	1	2026-02-03T06:46:03Z
`autodiscover.kis1.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`autodiscover.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`backup-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`backup.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`backup.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`bankettprofi.uke.de`	CT Log	Current	`srvw1prxav-reverse.uke.de`	1	2025-12-01T16:42:39Z
`befragung.uke.de`	CT Log	Current	—	1	2025-11-19T14:51:20Z
`biobank-test.fit.uke.de`	CT Log	Current	`srvw1prxav-reverse.uke.de`	1	2025-12-01T16:41:41Z
`biobank.fit.uke.de`	CT Log	Current	—	1	2025-12-01T16:41:41Z
`box-test.uke.de`	CT Log	Current	—	2	2025-11-19T06:18:11Z
`box.uke.de`	CT Log	Current	—	2	2025-11-19T06:18:11Z
`callme.uke.de`	CT Log	Current	—	1	2025-05-21T13:47:56Z
`campuscan.uke.de`	CT Log	Current	—	1	2025-11-03T10:35:46Z
`caresyntax-test.uke.de`	CT Log	Current	—	1	2025-12-09T08:42:36Z
`caresyntax.uke.de`	CT Log	Current	—	1	2025-12-09T08:42:36Z
`castor.uke.de`	CT Log	Current	—	1	2025-12-01T16:40:55Z
`castortest.uke.de`	CT Log	Current	—	1	2025-12-01T16:40:55Z
`ceph.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`ceph.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`chat-fit.uke.de`	CT Log	Current	—	3	2025-05-02T12:09:10Z
`chat.fit.uke.de`	CT Log	Current	—	1	2025-12-09T07:56:05Z
`cms-neu.uke.de`	CT Log	Current	—	1	2026-03-04T08:44:40Z
`cms-schulung.uke.de`	CT Log	Current	—	1	2025-11-24T15:08:54Z
`cms.uke.de`	CT Log	Current	—	1	2026-03-04T08:44:40Z
`cmsprev.uke.de`	CT Log	Current	—	1	2025-11-24T15:37:28Z
`coder-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`coder.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`coder.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`collab-edge.uke.de`	CT Log	Current	—	3	2025-05-21T14:11:04Z
`collabora.fit.uke.de`	CT Log	Current	—	1	2025-08-13T09:39:51Z
`collaboration.fit.uke.de`	CT Log	Current	—	1	2025-08-13T09:39:51Z
`cs-anforderung-test.uke.de`	CT Log	Current	—	1	2025-12-01T16:40:41Z
`cs-anforderung.uke.de`	CT Log	Current	—	1	2025-12-01T16:40:41Z
`cumulus.uke.de`	CT Log	Current	—	1	2025-12-01T16:42:51Z
`dashboard.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`dashboard.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`datenhotel-jhub-test.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:31Z
`datenhotel-jhub.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:31Z
`datenhotel-test.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:31Z
`datenhotel.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:31Z
`dekanet.uke.de`	CT Log	Current	—	1	2025-11-04T09:30:53Z
`dekanite.uke.de`	CT Log	Current	—	1	2025-11-04T09:30:08Z
`deprecatedstorage.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`deprecatedstorage.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`dsf-bpe-test.fit.uke.de`	CT Log	Current	—	1	2025-12-01T11:30:53Z
`dsf-bpe.fit.uke.de`	CT Log	Current	—	1	2025-12-01T11:30:53Z
`dsf-fhir-test.fit.uke.de`	CT Log	Current	—	1	2025-07-23T15:05:43Z
`dsf-fhir.fit.uke.de`	CT Log	Current	—	1	2025-07-23T15:05:43Z
`ecp.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`elearning.uke.de`	CT Log	Current	—	1	2025-11-04T09:29:26Z
`erecover-thera.uke.de`	CT Log	Current	—	1	2025-12-01T16:43:03Z
`erecover.uke.de`	CT Log	Current	`srvw1prxav-reverse.uke.de`	1	2025-12-01T16:43:03Z
`etraining.uke.de`	CT Log	Current	—	1	2025-11-04T09:29:39Z
`ews.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`exam.agav.uke.de`	CT Log	Current	—	1	2025-03-25T10:15:35Z
`fatdepot.gwis.uke.de`	CT Log	Current	—	1	2025-06-18T09:24:58Z
`fernwartung-test.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:53Z
`fernwartung.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:53Z
`fewa-box01.uke.de`	CT Log	Current	—	1	2025-12-01T16:42:16Z
`fider.uke.de`	CT Log	Current	—	1	2026-02-19T11:03:10Z
`fis.uke.de`	CT Log	Current	—	1	2025-11-04T09:29:52Z
`fistest.uke.de`	CT Log	Current	—	1	2025-11-04T09:27:54Z
`fit-test.uke.de`	CT Log	Current	—	2	2025-07-29T09:36:18Z
`fit.uke.de`	CT Log	Current	—	2	2025-07-29T09:35:35Z
`fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`fitgwp.uke.de`	CT Log	Current	—	1	2025-05-02T12:09:10Z
`fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`fitwiki.fit.uke.de`	CT Log	Current	—	1	2025-12-09T07:56:05Z
`flyte.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`flyte.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`followme-pin.uke.de`	CT Log	Current	—	1	2025-12-09T08:42:51Z
`fortbildung.uke.de`	CT Log	Current	—	1	2025-10-16T13:19:14Z
`fragebogen-hchs.uke.de`	CT Log	Current	—	1	2026-02-05T08:16:54Z
`germanvasc.uke.de`	CT Log	Current	—	1	2025-10-16T13:18:59Z
`getmyqrcode.uke.de`	CT Log	Current	—	1	2025-10-06T11:30:11Z
`getppr-test.uke.de`	CT Log	Current	—	1	2025-11-11T08:42:57Z
`getppr.uke.de`	CT Log	Current	—	1	2025-04-03T13:13:50Z
`gitea.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`gitea.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`gitlab-fit.uke.de`	CT Log	Current	—	3	2025-05-05T09:58:15Z
`gitlab-minio-fit.uke.de`	CT Log	Current	—	3	2025-05-05T09:58:15Z
`gitlab-pages-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`gitlab-registry-fit.uke.de`	CT Log	Current	—	3	2025-05-05T09:58:15Z
`gitlab.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`gitlab.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`gwis-access-test.uke.de`	CT Log	Current	—	4	2025-07-29T09:35:35Z
`gwis-access.uke.de`	CT Log	Current	—	4	2025-07-29T09:35:35Z
`h3-gateway-test.uke.de`	CT Log	Current	—	1	2025-11-13T08:14:51Z
`h3-repository-test.uke.de`	CT Log	Current	—	1	2025-11-13T08:14:51Z
`i2transhealth.uke.de`	CT Log	Current	—	1	2025-12-01T16:43:03Z
`iamsnipeit.gwis.uke.de`	CT Log	Current	—	1	2025-03-13T14:06:58Z
`ianeu-nas-2.gwis.uke.de`	CT Log	Current	—	1	2025-10-17T13:16:22Z
`ibmznasn25.gwis.uke.de`	CT Log	Current	—	1	2025-11-03T10:34:46Z
`ibsnas01.gwis.uke.de`	CT Log	Current	—	1	2025-10-17T13:16:52Z
`icns-nas1.uke.de`	CT Log	Current	—	1	2025-07-17T08:06:47Z
`icns-nas2.uke.de`	CT Log	Current	—	1	2025-09-12T06:37:02Z
`icns-nas3.uke.de`	CT Log	Current	—	1	2025-10-08T11:52:40Z
`icns-overleaf.uke.de`	CT Log	Current	—	1	2025-09-12T06:37:26Z
`imap.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`imbeamgticket.gwis.uke.de`	CT Log	Current	—	1	2025-06-10T06:49:56Z
`imbefs.uke.de`	CT Log	Current	—	1	2025-12-03T16:54:35Z
`imbefs2.gwis.uke.de`	CT Log	Current	—	1	2025-12-03T16:54:48Z
`imbesc.uke.de`	CT Log	Current	—	1	2025-11-25T13:51:58Z
`imbesnipeit.gwis.uke.de`	CT Log	Current	—	1	2025-03-14T05:57:52Z
`imed-campus.uke.de`	CT Log	Current	—	1	2025-11-04T09:31:55Z
`imed-stundenplan.uke.de`	CT Log	Current	—	1	2025-11-04T09:27:02Z
`increase.uke.de`	CT Log	Current	—	1	2025-12-01T16:40:06Z
`infra.uke.de`	CT Log	Current	—	2	2025-04-25T09:31:31Z
`intranet.uke.de`	CT Log	Current	—	1	2025-11-24T15:07:52Z
`isms.uke.de`	CT Log	Current	—	1	2025-12-01T16:42:28Z
`it-infopoint-test.uke.de`	CT Log	Current	—	1	2026-01-14T13:54:01Z
`it-infopoint.uke.de`	CT Log	Current	—	1	2026-01-14T13:54:01Z
`it-service-int.uke.de`	CT Log	Current	—	1	2025-11-19T14:51:32Z
`it-service-kon.uke.de`	CT Log	Current	—	1	2025-11-19T14:51:32Z
`it-service-test.uke.de`	CT Log	Current	—	1	2025-11-19T14:51:32Z
`it-service.uke.de`	CT Log	Current	—	1	2025-11-19T14:51:32Z
`itest-campus-p1.uke.de`	CT Log	Current	—	1	2025-11-04T09:27:41Z
`itest-campus-std.uke.de`	CT Log	Current	—	1	2025-11-04T09:29:06Z
`itest-campus-t1.uke.de`	CT Log	Current	—	1	2025-11-03T10:36:05Z
`itmacmanager.uke.de`	CT Log	Current	—	1	2025-12-01T16:41:18Z
`itsm-kon.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:17Z
`itsm-test.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:17Z
`itsm.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:17Z
`jobs-test.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:42Z
`jobs.uke.de`	CT Log	Current	—	4	2025-11-17T07:51:29Z
`join.uke.de`	CT Log	Current	—	3	2025-05-21T14:11:04Z
`jukebox-test.uke.de`	CT Log	Current	—	1	2025-12-01T16:43:30Z
`jukebox.uke.de`	CT Log	Current	—	1	2025-12-01T16:43:30Z
`jupyterhub.uke.de`	CT Log	Current	—	2	2025-07-18T05:12:41Z
`kanban.fit.uke.de`	CT Log	Current	—	1	2025-12-09T07:56:05Z
`kc-bak.gwis.uke.de`	CT Log	Current	—	1	2026-02-24T12:21:32Z
`kc-bak.klch.gwis.uke.de`	CT Log	Current	—	1	2026-02-24T12:21:32Z
`keyauth-test.uke.de`	CT Log	Current	—	1	2025-10-27T17:14:24Z
`keyauth.uke.de`	CT Log	Current	—	1	2025-10-27T17:14:24Z
`kis2vpn-mobile.uke.de`	CT Log	Current	—	2	2025-11-19T14:52:39Z
`kis2vpn-test.uke.de`	CT Log	Current	—	2	2025-11-19T14:52:39Z
`kis2vpn.uke.de`	CT Log	Current	—	2	2025-11-19T14:52:39Z
`kisabt-focalpoint.uke.de`	CT Log	Current	—	1	2025-06-23T12:31:59Z
`kisx-ext.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:16Z
`klch.gwis.uke.de`	CT Log	Current	—	1	2026-02-24T12:21:32Z
`kle-sorter.uke.de`	CT Log	Current	—	1	2025-12-01T16:40:30Z
`klinche.uke.de`	CT Log	Current	—	1	2026-02-03T12:45:10Z
`konferenzbuchung.uke.de`	CT Log	Current	—	1	2025-12-01T16:40:18Z
`kontaktkompass.uke.de`	CT Log	Current	—	1	2025-11-24T15:08:28Z
`kube-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`laborbuch.uke.de`	CT Log	Current	—	5	2025-04-01T11:39:04Z
`lb-owa.uke.de`	CT Log	Current	—	1	2025-11-19T14:52:53Z
`ldap-ext.uke.de`	CT Log	Current	—	1	2025-11-24T15:08:17Z
`learn.uke.de`	CT Log	Current	—	2	2026-02-24T12:21:58Z
`lecare.uke.de`	CT Log	Current	—	1	2025-11-11T08:05:55Z
`login-test.fit.uke.de`	CT Log	Current	—	1	2025-12-01T16:43:15Z
`login.fit.uke.de`	CT Log	Current	—	1	2025-12-01T16:43:15Z
`mail.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`mailin.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`mailrelay.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`mapi.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`mas-fit.uke.de`	CT Log	Current	—	3	2025-05-02T12:09:10Z
`matrix-fit.uke.de`	CT Log	Current	—	3	2025-05-02T12:09:10Z
`matrix-test.uke.de`	CT Log	Current	—	1	2025-12-02T14:09:29Z
`matrix.uke.de`	CT Log	Current	—	1	2025-12-02T14:09:29Z
`mein.uke.de`	CT Log	Current	—	1	2025-07-25T11:12:31Z
`meldeportal-entwicklung.uke.de`	CT Log	Current	—	1	2026-02-09T09:17:35Z
`meldeportal-konsolidierung.uke.de`	CT Log	Current	—	1	2026-02-09T09:17:35Z
`meldeportal.uke.de`	CT Log	Current	—	1	2026-02-09T09:17:35Z
`mfit-assets.uke.de`	CT Log	Current	—	1	2026-01-08T08:37:16Z
`mfit-code.uke.de`	CT Log	Current	—	1	2025-11-04T09:31:40Z
`mfit-monitor.uke.de`	CT Log	Current	—	1	2026-01-08T08:37:01Z
`mfit-next.uke.de`	CT Log	Current	—	1	2025-11-04T09:26:48Z
`mfit-service.uke.de`	CT Log	Current	—	1	2025-11-04T09:26:34Z
`mfit-warden.uke.de`	CT Log	Current	—	1	2026-01-08T08:36:50Z
`mfit-web.uke.de`	CT Log	Current	—	1	2025-11-04T09:28:11Z
`min-cloud.uke.de`	CT Log	Current	—	1	2025-12-01T16:41:07Z
`mobile.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`mrtc-fit.uke.de`	CT Log	Current	—	3	2025-05-02T12:09:10Z
`mtb-auth.uke.de`	CT Log	Current	—	4	2025-04-28T13:05:50Z
`mtb-bioinf.uke.de`	CT Log	Current	—	4	2025-04-28T13:05:50Z
`mtb-bwhc.uke.de`	CT Log	Current	—	4	2025-04-28T13:05:50Z
`mtb-dnpm-dip.uke.de`	CT Log	Current	—	4	2025-04-28T13:05:50Z
`mtb-gen.uke.de`	CT Log	Current	—	4	2025-04-28T13:05:50Z
`mtb-icd10.uke.de`	CT Log	Current	—	2	2025-04-28T13:05:50Z
`mtb-kc.uke.de`	CT Log	Current	—	4	2025-04-28T13:05:50Z
`mtb-path.uke.de`	CT Log	Current	—	4	2025-04-28T13:05:50Z
`mtb-rc-dnpm-dip.uke.de`	CT Log	Current	—	1	2025-10-23T05:51:28Z
`mtb-rc-kc.uke.de`	CT Log	Current	—	1	2025-10-23T05:51:28Z
`mtb-rc.uke.de`	CT Log	Current	—	2	2025-06-30T15:02:37Z
`mtb.uke.de`	CT Log	Current	—	4	2025-04-28T05:34:43Z
`myphone.uke.de`	CT Log	Current	—	1	2025-12-02T09:46:23Z
`myphoto-hchs.uke.de`	CT Log	Current	—	1	2025-10-16T13:18:41Z
`mysite.uke.de`	CT Log	Current	—	3	2025-11-25T16:42:34Z
`nida-test.uke.de`	CT Log	Current	—	1	2025-12-01T16:41:53Z
`nida.uke.de`	CT Log	Current	—	1	2025-12-01T16:41:53Z
`ntfy.uke.de`	CT Log	Current	—	1	2025-11-17T07:52:46Z
`oab.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`occ-laborbuch.uke.de`	CT Log	Current	—	1	2025-10-08T09:13:47Z
`oos-laborbuch.uke.de`	CT Log	Current	—	3	2025-07-16T14:15:29Z
`oos.uke.de`	CT Log	Current	—	1	2025-11-24T15:08:40Z
`op-dekanat.uke.de`	CT Log	Current	—	1	2025-11-04T09:31:07Z
`openstack-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`openstack.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`openstack.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`orpheus-test.kis1.uke.de`	CT Log	Current	—	1	2025-06-12T13:38:52Z
`orpheus-test.uke.de`	CT Log	Current	—	1	2025-06-12T13:38:52Z
`orpheus.kis1.uke.de`	CT Log	Current	—	1	2025-06-12T13:38:52Z
`orpheus.uke.de`	CT Log	Current	—	1	2025-06-12T13:38:52Z
`osc-api.gwis.uke.de`	CT Log	Current	—	2	2025-07-29T13:13:12Z
`parken.uke.de`	CT Log	Current	—	1	2025-12-02T09:45:40Z
`partner-test.uke.de`	CT Log	Current	—	1	2025-07-25T11:12:31Z
`partner.uke.de`	CT Log	Current	—	1	2025-07-25T11:12:31Z
`pathopool.uke.de`	CT Log	Current	—	1	2025-09-12T06:59:56Z
`pathoslide.uke.de`	CT Log	Current	—	1	2025-10-06T11:30:54Z
`patmonweb.kisabt.uke.de`	CT Log	Current	—	1	2025-12-17T06:19:12Z
`pb-ambulanz.uke.de`	CT Log	Current	—	1	2025-12-02T09:45:13Z
`personalservices-entwicklung-extern.uke.de`	CT Log	Current	—	1	2025-11-19T14:51:43Z
`personalservices-entwicklung.uke.de`	CT Log	Current	—	1	2025-12-02T09:46:13Z
`personalservices-extern.uke.de`	CT Log	Current	`srvwdrv11-reverse.uke.de`	1	2025-11-19T14:51:43Z
`personalservices-konsolidierung-extern.uke.de`	CT Log	Current	—	1	2025-11-19T14:51:43Z
`personalservices-konsolidierung.uke.de`	CT Log	Current	—	1	2025-12-02T09:46:13Z
`personalservices.uke.de`	CT Log	Current	—	1	2025-12-02T09:46:13Z
`pffportal.uke.de`	CT Log	Current	—	1	2025-11-04T09:30:39Z
`pfftestportal.uke.de`	CT Log	Current	—	2	2025-08-27T12:49:12Z
`pjlb-test.uke.de`	CT Log	Current	—	1	2025-11-04T09:26:19Z
`pjlogbuch.uke.de`	CT Log	Current	—	1	2025-11-04T09:30:26Z
`pop.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`portal-test-intranet.uke.de`	CT Log	Current	—	1	2025-03-25T11:04:55Z
`portal-test-laborbuch.uke.de`	CT Log	Current	—	1	2025-03-25T10:04:38Z
`portal-test.uke.de`	CT Log	Current	—	1	2025-10-06T11:30:26Z
`portal.uke.de`	CT Log	Current	—	1	2025-10-06T11:30:26Z
`portalowa.kis1.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`project.fit.uke.de`	CT Log	Current	—	1	2025-12-02T09:46:45Z
`promotion.uke.de`	CT Log	Current	—	2	2025-04-24T13:09:13Z
`proxy.uke.de`	DNS	Current	`bluecoat.uke.de`	—	—	—
`prz.uke.de`	CT Log	Current	—	1	2025-11-04T09:28:30Z
`psobest.uke.de`	CT Log	Current	—	1	2025-12-02T09:47:43Z
`qm-extern.uke.de`	CT Log	Current	—	2	2025-05-12T08:54:43Z
`qm-handbuch.uke.de`	CT Log	Current	—	2	2025-10-16T10:54:55Z
`qm.uke.de`	CT Log	Current	—	1	2025-05-12T08:54:43Z
`raumcockpit-test.uke.de`	CT Log	Current	—	1	2026-01-14T13:54:16Z
`raumcockpit.uke.de`	CT Log	Current	—	1	2026-01-14T13:54:16Z
`recruiting-test.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:42Z
`recruiting.uke.de`	CT Log	Current	—	3	2025-07-23T09:33:16Z
`redcap-hchs.uke.de`	CT Log	Current	—	1	2026-01-22T11:41:53Z
`redcap-mz-test.fit.uke.de`	CT Log	Current	—	1	2025-12-01T16:42:05Z
`redcap-mz.fit.uke.de`	CT Log	Current	`srvw1prxav-reverse.uke.de`	1	2025-12-01T16:42:05Z
`redcap-survey.fit.uke.de`	CT Log	Current	—	1	2025-12-02T09:45:52Z
`redcap-test.fit.uke.de`	CT Log	Current	`redcap.fit.uke.de`	1	2025-12-02T09:45:52Z
`redcap.fit.uke.de`	CT Log	Current	—	1	2025-12-02T09:45:52Z
`roxtra.mibi.gwis.uke.de`	CT Log	Current	—	1	2025-11-24T08:20:31Z
`sapboportal-test.uke.de`	CT Log	Current	—	1	2025-12-02T09:44:59Z
`sapboportal-vip.uke.de`	CT Log	Current	—	1	2025-09-29T12:29:43Z
`sapbwportal.uke.de`	CT Log	Current	—	1	2025-10-06T11:31:07Z
`sapwk2pm-vip.uke.de`	CT Log	Current	—	1	2025-12-02T09:47:53Z
`sapwp2pm-vip.uke.de`	CT Log	Current	`srvw1prxav-reverse.uke.de`	1	2025-12-02T09:47:53Z
`sapwt2pm-vip.uke.de`	CT Log	Current	—	1	2025-12-02T09:47:53Z
`sdntt.uke.de`	CT Log	Current	—	1	2025-12-02T09:47:14Z
`sechub.uke.de`	CT Log	Current	—	1	2025-12-02T09:46:54Z
`secmail.uke.de`	CT Log	Current	—	1	2025-09-29T12:28:52Z
`sectra-test.uke.de`	CT Log	Current	—	1	2025-12-09T07:56:30Z
`sectra.uke.de`	CT Log	Current	—	1	2025-12-09T07:56:30Z
`server01.gwis.uke.de`	CT Log	Current	—	1	2025-10-29T07:04:21Z
`server02.gwis.uke.de`	CT Log	Current	—	1	2025-10-29T07:04:44Z
`services.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`services.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`sfbcluster224.uke.de`	CT Log	Current	—	1	2025-12-02T09:45:30Z
`slidecenter.uke.de`	CT Log	Current	—	1	2025-12-02T09:45:21Z
`smtp.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`spexpert-p.uke.de`	CT Log	Current	—	1	2025-12-02T09:48:20Z
`srv-infra-p01.kdmz4.uke.de`	CT Log	Current	—	1	2025-09-17T06:57:23Z
`srv-infra-p02.kdmz4.uke.de`	CT Log	Current	—	1	2025-09-17T06:57:23Z
`srv-time-1.kis1.uke.de`	CT Log	Current	—	1	2025-08-29T11:53:07Z
`srv-time-2.kis1.uke.de`	CT Log	Current	—	1	2025-08-29T11:53:27Z
`srv-time-3.kis1.uke.de`	CT Log	Current	—	1	2025-08-29T11:53:40Z
`srv-time-4.kis1.uke.de`	CT Log	Current	—	1	2025-08-29T11:53:53Z
`srv-ufmgmt-p01-vip.dmz.kis1.uke.de`	CT Log	Current	—	1	2025-12-09T08:42:51Z
`srv-vcgwis-p1.gwis.uke.de`	CT Log	Current	—	2	2025-07-17T08:09:09Z
`srv-vcgwis-t1.gwis.uke.de`	CT Log	Current	—	1	2025-08-13T09:40:07Z
`srvdxdoxisappp1.kis1.uke.de`	CT Log	Current	—	1	2025-10-17T15:33:28Z
`srvewaye01.kdmz7.uke.de`	CT Log	Current	—	3	2025-05-21T14:11:04Z
`srvewaye01.uke.de`	CT Log	Current	—	3	2025-05-21T14:11:04Z
`srvewaye02.uke.de`	CT Log	Current	—	1	2025-05-21T13:47:56Z
`srvkdinswebp01.dmz.kis1.uke.de`	CT Log	Current	—	1	2025-09-17T06:57:23Z
`srvkdqifappp1.kis1.uke.de`	CT Log	Current	—	1	2025-05-12T08:54:43Z
`srvkdxprclejp01.uke.de`	CT Log	Current	—	1	2025-05-21T13:47:56Z
`srvkdxprclemp01.uke.de`	CT Log	Current	—	3	2025-05-21T14:11:04Z
`srvkdxprwayep03.kdmz7.uke.de`	CT Log	Current	—	3	2025-05-21T14:11:04Z
`srvkdxprwayep03.uke.de`	CT Log	Current	—	3	2025-05-21T14:11:04Z
`srvkdxprwayep04.uke.de`	CT Log	Current	—	1	2025-05-21T13:47:56Z
`srvw1prxavp1.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:52Z
`srvw1prxavp2.uke.de`	CT Log	Current	—	1	2025-12-09T07:55:52Z
`srvwdcsaappk02.uke.de`	CT Log	Current	—	1	2025-10-08T13:48:28Z
`srvwdcsaappp02.uke.de`	CT Log	Current	—	1	2025-10-08T13:48:28Z
`srvwdinsast1.uke.de`	CT Log	Current	—	1	2025-11-19T14:51:55Z
`srvwdvmsstrmp1.uke.de`	CT Log	Current	—	1	2026-02-09T06:20:35Z
`srvwdwwwfee1.uke.de`	CT Log	Current	—	1	2025-08-27T06:34:36Z
`status-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`storage-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`storage.fit.uke.de`	CT Log	Current	—	1	2025-08-11T13:44:43Z
`storage.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`storage.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`storages.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`storages.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`strocare.uke.de`	CT Log	Current	—	1	2025-12-02T09:48:10Z
`sts-sso.uke.de`	CT Log	Current	—	1	2025-11-19T14:52:05Z
`studmail.uke.de`	CT Log	Current	—	1	2025-11-19T14:53:42Z
`superserverizip.gwis.uke.de`	CT Log	Current	—	1	2025-10-27T12:01:13Z
`survey.fit.uke.de`	CT Log	Current	—	1	2025-12-02T09:45:52Z
`survey.uke.de`	CT Log	Current	—	1	2025-12-02T09:45:13Z
`synods918agadh.gwis.uke.de`	CT Log	Current	—	1	2026-03-04T12:14:24Z
`tableau.fit.uke.de`	CT Log	Current	—	1	2025-09-29T12:29:26Z
`taiga-hchs.uke.de`	CT Log	Current	—	1	2025-08-26T08:30:36Z
`terminal-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`test-kanban.fit.uke.de`	CT Log	Current	—	1	2025-12-09T07:56:05Z
`testbox.uke.de`	CT Log	Current	—	1	2025-12-01T16:41:29Z
`testcampuscan.uke.de`	CT Log	Current	—	1	2025-11-03T10:35:29Z
`testetraining.uke.de`	CT Log	Current	—	1	2026-01-08T08:36:29Z
`testo-pucit.uke.de`	CT Log	Current	—	1	2025-12-02T09:47:04Z
`testwiki1.fit.uke.de`	CT Log	Current	—	1	2025-12-09T07:56:05Z
`testwiki2.fit.uke.de`	CT Log	Current	—	1	2025-12-09T07:56:05Z
`tim-admin.uke.de`	CT Log	Current	—	1	2025-12-02T14:09:29Z
`tim-auth.uke.de`	CT Log	Current	—	1	2025-12-02T14:09:29Z
`tim-mon.uke.de`	CT Log	Current	—	1	2025-12-02T14:09:29Z
`tim-test-admin.uke.de`	CT Log	Current	`srvw1prxav-reverse.uke.de`	1	2025-12-02T14:09:29Z
`tim-test-auth.uke.de`	CT Log	Current	—	1	2025-12-02T14:09:29Z
`tim-test.uke.de`	CT Log	Current	—	1	2025-12-02T14:09:29Z
`tim.uke.de`	CT Log	Current	—	1	2025-12-02T14:09:29Z
`tracking.uke.de`	CT Log	Current	—	1	2025-12-02T09:46:35Z
`transferstelle-test.fit.uke.de`	CT Log	Current	—	1	2025-12-02T09:46:02Z
`transferstelle.fit.uke.de`	CT Log	Current	—	1	2025-12-02T09:46:02Z
`treuhandstelle-test.uke.de`	CT Log	Current	—	1	2025-12-02T09:47:23Z
`treuhandstelle.uke.de`	CT Log	Current	—	1	2025-12-02T09:47:23Z
`turing.uke.de`	CT Log	Current	—	2	2025-09-18T12:47:41Z
`ucchbk-admin.uke.de`	CT Log	Current	—	1	2025-06-11T14:00:10Z
`ucchbk.uke.de`	CT Log	Current	—	1	2025-06-11T14:00:10Z
`ucs1.uke.de`	CT Log	Current	—	3	2025-05-21T14:11:04Z
`uem-as.uke.de`	CT Log	Current	—	2	2025-10-27T17:14:00Z
`uem-at.uke.de`	CT Log	Current	—	2	2025-10-27T17:14:00Z
`uem-at01.uke.de`	CT Log	Current	—	1	2025-10-30T14:06:40Z
`uem-at02.uke.de`	CT Log	Current	—	1	2025-10-30T14:06:40Z
`uem.uke.de`	CT Log	Current	—	2	2025-10-27T17:14:00Z
`uemt-as.uke.de` 443/tcp https	CT Log	Current	—	1	2025-10-27T17:14:00Z
`uemt-at.uke.de`	CT Log	Current	—	1	2025-10-27T17:14:00Z
`uemt.uke.de`	CT Log	Current	—	1	2025-10-27T17:14:00Z
`umfrage.fit.uke.de`	CT Log	Current	—	1	2025-12-02T09:45:52Z
`vcenter-lab.gwis.uke.de`	CT Log	Current	—	1	2025-12-02T09:47:33Z
`vcenter-prod.gwis.uke.de`	CT Log	Current	—	1	2025-12-02T09:47:33Z
`vcenter.gwis.uke.de`	CT Log	Current	—	2	2025-07-17T08:09:09Z
`wblb-test.uke.de`	CT Log	Current	—	1	2025-11-04T09:28:47Z
`wblogbuch.uke.de`	CT Log	Current	—	2	2025-11-04T09:32:13Z
`webdav.fragebogen-hchs.uke.de`	CT Log	Current	—	1	2026-02-05T08:16:54Z
`webmail.uke.de`	CT Log	Current	—	1	2025-11-24T12:35:36Z
`wellknown-fit.uke.de`	CT Log	Current	—	3	2025-05-02T12:09:10Z
`wis-rad.uke.de`	CT Log	Current	—	1	2025-10-27T10:00:15Z
`wisvpn.uke.de`	CT Log	Current	—	1	2025-11-19T14:52:20Z
`wopiserver.fit.uke.de`	CT Log	Current	—	1	2025-08-13T09:39:51Z
`workflow-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`workflow.fitgwp.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:58:29Z
`workflow.fitgwt.gwis.uke.de`	CT Log	Current	—	4	2025-03-27T10:57:59Z
`www-schulung.uke.de`	CT Log	Current	—	1	2025-11-11T08:11:01Z
`www-test.uke.de`	CT Log	Current	—	1	2025-08-27T06:34:36Z
`www.aaa.uke.de`	CT Log	Current	—	1	2026-02-03T06:46:03Z
`www.auth.uke.de`	CT Log	Current	—	1	2026-02-03T06:46:03Z
`www.backup-fit.uke.de`	CT Log	Current	—	1	2025-05-05T09:58:15Z
`www.box-test.uke.de`	CT Log	Current	—	2	2025-11-19T06:18:11Z
`www.box.uke.de`	CT Log	Current	—	2	2025-11-19T06:18:11Z
`www.callme.uke.de`	CT Log	Current	—	1	2025-05-21T13:47:56Z
`www.chat-fit.uke.de`	CT Log	Current	—	2	2025-05-02T12:09:10Z
`www.coder-fit.uke.de`	CT Log	Current	—	1	2025-05-05T09:58:15Z
`www.collab-edge.uke.de`	CT Log	Current	—	2	2025-05-21T14:11:04Z
`www.collabora.fit.uke.de`	CT Log	Current	—	1	2025-08-13T09:39:51Z
`www.collaboration.fit.uke.de`	CT Log	Current	—	1	2025-08-13T09:39:51Z
`www.dsf-fhir-test.fit.uke.de`	CT Log	Current	—	1	2025-07-23T15:05:43Z
`www.dsf-fhir.fit.uke.de`	CT Log	Current	—	1	2025-07-23T15:05:43Z
`www.exam.agav.uke.de`	CT Log	Current	—	1	2025-03-25T10:15:35Z
`www.fatdepot.gwis.uke.de`	CT Log	Current	—	1	2025-06-18T09:24:58Z
`www.fitgwp.uke.de`	CT Log	Current	—	1	2025-05-02T12:09:10Z
`www.fragebogen-hchs.uke.de`	CT Log	Current	—	1	2026-02-05T08:16:54Z
`www.getppr-test.uke.de`	CT Log	Current	—	1	2025-11-11T08:42:57Z
`www.getppr.uke.de`	CT Log	Current	—	1	2025-04-03T13:13:50Z
`www.gitlab-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`www.gitlab-minio-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`www.gitlab-pages-fit.uke.de`	CT Log	Current	—	1	2025-05-05T09:58:15Z
`www.gitlab-registry-fit.uke.de`	CT Log	Current	—	2	2025-05-05T09:58:15Z
`www.h3-gateway-test.uke.de`	CT Log	Current	—	1	2025-11-13T08:14:51Z
`www.h3-repository-test.uke.de`	CT Log	Current	—	1	2025-11-13T08:14:51Z
`www.iamsnipeit.gwis.uke.de`	CT Log	Current	—	1	2025-03-13T14:06:58Z
`www.ianeu-nas-2.gwis.uke.de`	CT Log	Current	—	1	2025-10-17T13:16:22Z
`www.ibmznasn25.gwis.uke.de`	CT Log	Current	—	1	2025-11-03T10:34:46Z
`www.ibsnas01.gwis.uke.de`	CT Log	Current	—	1	2025-10-17T13:16:52Z
`www.icns-nas1.uke.de`	CT Log	Current	—	1	2025-07-17T08:06:47Z
`www.icns-nas2.uke.de`	CT Log	Current	—	1	2025-09-12T06:37:02Z
`www.icns-nas3.uke.de`	CT Log	Current	—	1	2025-10-08T11:52:40Z
`www.icns-overleaf.uke.de`	CT Log	Current	—	1	2025-09-12T06:37:26Z
`www.imbeamgticket.gwis.uke.de`	CT Log	Current	—	1	2025-06-10T06:49:56Z
`www.imbefs.uke.de`	CT Log	Current	—	1	2025-12-03T16:54:35Z
`www.imbefs2.gwis.uke.de`	CT Log	Current	—	1	2025-12-03T16:54:48Z
`www.imbesc.uke.de`	CT Log	Current	—	1	2025-11-25T13:51:58Z
`www.imbesnipeit.gwis.uke.de`	CT Log	Current	—	1	2025-03-14T05:57:52Z
`www.it-infopoint-test.uke.de`	CT Log	Current	—	1	2026-01-14T13:54:01Z
`www.it-infopoint.uke.de`	CT Log	Current	—	1	2026-01-14T13:54:01Z
`www.jobs.uke.de`	CT Log	Current	—	2	2025-11-17T07:51:29Z
`www.join.uke.de`	CT Log	Current	—	2	2025-05-21T14:11:04Z
`www.jupyterhub.uke.de`	CT Log	Current	—	1	2025-07-18T05:12:41Z
`www.kisabt-focalpoint.uke.de`	CT Log	Current	—	1	2025-06-23T12:31:59Z
`www.kube-fit.uke.de`	CT Log	Current	—	1	2025-05-05T09:58:15Z
`www.learn.uke.de`	CT Log	Current	—	2	2026-02-24T12:21:58Z
`www.lecare.uke.de`	CT Log	Current	—	1	2025-11-11T08:05:55Z
`www.mas-fit.uke.de`	CT Log	Current	—	2	2025-05-02T12:09:10Z
`www.matrix-fit.uke.de`	CT Log	Current	—	2	2025-05-02T12:09:10Z
`www.mein.uke.de`	CT Log	Current	—	1	2025-07-25T11:12:31Z
`www.mrtc-fit.uke.de`	CT Log	Current	—	2	2025-05-02T12:09:10Z
`www.mtb-auth.uke.de`	CT Log	Current	—	1	2025-04-28T13:05:50Z
`www.mtb-bioinf.uke.de`	CT Log	Current	—	1	2025-04-28T13:05:50Z
`www.mtb-bwhc.uke.de`	CT Log	Current	—	1	2025-04-28T13:05:50Z
`www.mtb-dnpm-dip.uke.de`	CT Log	Current	—	1	2025-04-28T13:05:50Z
`www.mtb-gen.uke.de`	CT Log	Current	—	1	2025-04-28T13:05:50Z
`www.mtb-icd10.uke.de`	CT Log	Current	—	1	2025-04-28T13:05:50Z
`www.mtb-kc.uke.de`	CT Log	Current	—	1	2025-04-28T13:05:50Z
`www.mtb-path.uke.de`	CT Log	Current	—	1	2025-04-28T13:05:50Z
`www.mtb.uke.de`	CT Log	Current	—	1	2025-04-28T05:34:43Z
`www.mysite.uke.de`	CT Log	Current	—	2	2025-11-25T16:42:34Z
`www.openstack-fit.uke.de`	CT Log	Current	—	1	2025-05-05T09:58:15Z
`www.partner-test.uke.de`	CT Log	Current	—	1	2025-07-25T11:12:31Z
`www.partner.uke.de`	CT Log	Current	—	1	2025-07-25T11:12:31Z
`www.pathopool.uke.de`	CT Log	Current	—	1	2025-09-12T06:59:56Z
`www.qm-handbuch.uke.de`	CT Log	Current	—	2	2025-10-16T10:54:55Z
`www.raumcockpit-test.uke.de`	CT Log	Current	—	1	2026-01-14T13:54:16Z
`www.raumcockpit.uke.de`	CT Log	Current	—	1	2026-01-14T13:54:16Z
`www.recruiting.uke.de`	CT Log	Current	—	1	2025-07-23T09:33:16Z
`www.roxtra.mibi.gwis.uke.de`	CT Log	Current	—	1	2025-11-24T08:20:31Z
`www.srv-vcgwis-p1.gwis.uke.de`	CT Log	Current	—	1	2025-07-17T08:09:09Z
`www.srvdxdoxisappp1.kis1.uke.de`	CT Log	Current	—	1	2025-10-17T15:33:28Z
`www.srvewaye01.kdmz7.uke.de`	CT Log	Current	—	2	2025-05-21T14:11:04Z
`www.srvewaye01.uke.de`	CT Log	Current	—	2	2025-05-21T14:11:04Z
`www.srvewaye02.uke.de`	CT Log	Current	—	1	2025-05-21T13:47:56Z
`www.srvkdxprclejp01.uke.de`	CT Log	Current	—	1	2025-05-21T13:47:56Z
`www.srvkdxprclemp01.uke.de`	CT Log	Current	—	2	2025-05-21T14:11:04Z
`www.srvkdxprwayep03.kdmz7.uke.de`	CT Log	Current	—	2	2025-05-21T14:11:04Z
`www.srvkdxprwayep03.uke.de`	CT Log	Current	—	2	2025-05-21T14:11:04Z
`www.srvkdxprwayep04.uke.de`	CT Log	Current	—	1	2025-05-21T13:47:56Z
`www.srvwdcsaappk02.uke.de`	CT Log	Current	—	1	2025-10-08T13:48:28Z
`www.srvwdcsaappp02.uke.de`	CT Log	Current	—	1	2025-10-08T13:48:28Z
`www.status-fit.uke.de`	CT Log	Current	—	1	2025-05-05T09:58:15Z
`www.storage-fit.uke.de`	CT Log	Current	—	1	2025-05-05T09:58:15Z
`www.storage.fit.uke.de`	CT Log	Current	—	1	2025-08-11T13:44:43Z
`www.superserverizip.gwis.uke.de`	CT Log	Current	—	1	2025-10-27T12:01:13Z
`www.synods918agadh.gwis.uke.de`	CT Log	Current	—	1	2026-03-04T12:14:24Z
`www.terminal-fit.uke.de`	CT Log	Current	—	1	2025-05-05T09:58:15Z
`www.turing.uke.de`	CT Log	Current	—	1	2025-11-06T18:34:57Z
`www.ucchbk-admin.uke.de`	CT Log	Current	—	1	2025-06-11T14:00:10Z
`www.ucchbk.uke.de`	CT Log	Current	—	1	2025-06-11T14:00:10Z
`www.ucs1.uke.de`	CT Log	Current	—	2	2025-05-21T14:11:04Z
`www.uke.de`	CT Log	Current	—	3	2025-05-21T14:11:04Z
`www.vcenter.gwis.uke.de`	CT Log	Current	—	1	2025-07-17T08:09:09Z
`www.webdav.fragebogen-hchs.uke.de`	CT Log	Current	—	1	2026-02-05T08:16:54Z
`www.wellknown-fit.uke.de`	CT Log	Current	—	2	2025-05-02T12:09:10Z
`www.wis-rad.uke.de`	CT Log	Current	—	1	2025-10-27T10:00:15Z
`www.wopiserver.fit.uke.de`	CT Log	Current	—	1	2025-08-13T09:39:51Z
`www.workflow-fit.uke.de`	CT Log	Current	—	1	2025-05-05T09:58:15Z
`www.www.jobs.uke.de`	CT Log	Current	—	1	2026-01-12T11:49:21Z
`www.www.recruiting.uke.de`	CT Log	Current	—	1	2025-07-23T09:33:16Z
`www.zem03.gwis.uke.de`	CT Log	Current	—	1	2025-10-17T13:17:10Z
`www.zemnas02.gwis.uke.de`	CT Log	Current	—	1	2025-10-17T13:16:38Z
`www.zfus-mfd-test.uke.de`	CT Log	Current	—	1	2025-11-11T08:42:44Z
`www.zfus-mfd.uke.de`	CT Log	Current	—	1	2025-11-11T08:42:44Z
`www.zusammenarbeit.uke.de`	CT Log	Current	—	1	2025-11-25T16:42:34Z
`wwwstat.uke.de`	CT Log	Current	—	1	2025-11-24T15:08:04Z
`zem03.gwis.uke.de`	CT Log	Current	—	1	2025-10-17T13:17:10Z
`zemnas02.gwis.uke.de`	CT Log	Current	—	1	2025-10-17T13:16:38Z
`zemwiki.fit.uke.de`	CT Log	Current	—	1	2025-12-09T07:56:05Z
`zfus-mfd-test.uke.de`	CT Log	Current	—	1	2025-11-11T08:42:44Z
`zfus-mfd.uke.de`	CT Log	Current	—	1	2025-11-11T08:42:44Z
`zusammenarbeit.uke.de`	CT Log	Current	—	2	2025-11-25T16:42:34Z
`zusammenarbeitsapps.uke.de`	CT Log	Current	—	4	2025-11-25T16:42:34Z
`zuse.uke.de`	CT Log	Current	—	1	2025-09-18T13:01:51Z

Export Recon (CSV)

Δ Changes Detected: TXT Resolver ≠ Authoritative (TTL / CDN rotation / recent change)

Risk: Low - typically resolves within TTL

DNS Intelligence What does DNS look like right now — and what changed over time?

DNS Evidence Diff Side-by-side comparison

Resolver Records (Public DNS cache)

Authoritative Records (Source of truth)

A Synchronized 1 / 1 records

134.100.186.245

AAAA 0 / 0 records

No records

CAA RFC 8659 §4 Synchronized 5 / 5 records

0 issuewild "harica.gr"

0 iodef "mailto:net-security@uke.de"

0 issue "harica.gr"

0 issuewild "harica.gr"

0 issue "sectigo.com"

0 issue "harica.gr"

0 issue "pki.dfn.de"

0 issue "sectigo.com"

0 iodef "mailto:net-security@uke.de"

0 issue "pki.dfn.de"

DMARC _dmarc.uke.de RFC 7489 §6.3 Synchronized 1 / 1 records

v=DMARC1; p=reject; adkim=r; aspf=r; ruf=mailto:dmarc-reports@uke.de

MX RFC 5321 Synchronized 2 / 2 records

0 iplexus1.uke.uni-hamburg.de.

0 iplexus2.uke.uni-hamburg.de.

NS RFC 1035 Synchronized 5 / 5 records

dns2.rrz.uni-hamburg.de.

netman.uke.uni-hamburg.de.

rzdspc1.informatik.uni-hamburg.de.

dns1.rrz.uni-hamburg.de.

dns-3.dfn.de.

rzdspc1.informatik.uni-hamburg.de.

dns1.rrz.uni-hamburg.de.

dns-3.dfn.de.

netman.uke.uni-hamburg.de.

dns2.rrz.uni-hamburg.de.

SOA RFC 1035 Synchronized 1 / 1 records

netman.uke.uni-hamburg.de. net-security.uke.de. 2026022700 10800 3600 2419200 7200

TXT RFC 7208 §4 Propagating 8 / 5 records

HARICA-ZhBU9ncDgtZ7MBJWiPY

HARICA-H5xiO7XVCKEPOQBDTcn

brevo-code:543fecfd7af25c0498807d050d3c2553

HARICA-QhKCSJkzCNyflY5R9Pc

brevo-code:543fecfd7af25c0498807d050d3c2553

apple-domain-verification=1GQjQjLP9HX5pIuQ

brevo-code:28b9a7401bb622df5de67e49fa7f2dda

+Rb+uEdewC04f3D77kvCwB569XYEXvgy0RbBUMr0N1ArwAj7KV1+zJM9z4DKVu/FdmP3UgQbh349d2t1t46Mfw==

—

v=spf1 mx ip4:134.100.101.8/30 ip4:134.100.53.70 ip4:134.100.53.101 ip4:134.100.38.112/30 ip4:188.138.124.28 ip4:62.245.148.4 ip4:94.199.88.64/26 ip4:94.199.90.64/26 ip4:134.119.253.31 ip4:217.113.45.225 ip4:85.13.149.7 include:spf.qb-feedback.com include:spf.protection.outlook.com include:spf.embloom.com -all

—

apple-domain-verification=1GQjQjLP9HX5pIuQ

—

DNS History Timeline BETA

Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key

Analyze Another Domain

Confirm Your Email Configuration

This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.

DATA FRESHNESS & METHODOLOGY

All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.

Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.

Intelligence Sources

This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.

Full List

Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.

71d3e8daaa6fa6f1d5b8d436f39ae18df53a3c13314556c9850aeaf6854862dccd19d0061b83e81f737fc961bd46cdcb13e8a4341b208cc1a6a9403bfd34ed0d

Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 7 Mar 2026, 23:32 UTC.

Download Raw Intelligence Download Checksum (.sha3)

Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.

After downloading, verify with any of these commands:

Tip: cd ~/Downloads first (or wherever you saved the files).

OpenSSL + Sidecar (macOS, Linux, WSL)

cat dns-intelligence-uke.de.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-uke.de.json

Python 3 (cross-platform)

python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-uke.de.json','rb').read()).hexdigest())"

sha3sum (coreutils 9+)

sha3sum -a 512 dns-intelligence-uke.de.json

Compare the output against the .sha3 file or the checksum API at /api/analysis/6374/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).

Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for uke.de. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.

DNS Records

Query A records (IPv4) RFC 1035

dig +noall +answer uke.de A

Query AAAA records (IPv6) RFC 1035

dig +noall +answer uke.de AAAA

Query MX records (mail servers) RFC 1035

dig +noall +answer uke.de MX

Query NS records (nameservers) RFC 1035

dig +noall +answer uke.de NS

Query TXT records RFC 1035

dig +noall +answer uke.de TXT

Email Authentication

Check SPF record RFC 7208

dig +short uke.de TXT | grep -i spf

Check DMARC policy RFC 7489

dig +short _dmarc.uke.de TXT

Check DKIM key for selector 'default' RFC 6376

dig +short default._domainkey.uke.de TXT

Check DKIM key for selector 'google' RFC 6376

dig +short google._domainkey.uke.de TXT

Check DKIM key for selector 'selector1' RFC 6376

dig +short selector1._domainkey.uke.de TXT

Check DKIM key for selector 'selector2' RFC 6376

dig +short selector2._domainkey.uke.de TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035

dig +dnssec +noall +answer uke.de DNSKEY

Check DNSSEC DS records RFC 4035

dig +noall +answer uke.de DS

Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035

dig +dnssec +cd uke.de A @1.1.1.1

Transport Security

Check TLSA record for iplexus1.uke.uni-hamburg.de RFC 7672

dig +noall +answer _25._tcp.iplexus1.uke.uni-hamburg.de TLSA

Check TLSA record for iplexus2.uke.uni-hamburg.de RFC 7672

dig +noall +answer _25._tcp.iplexus2.uke.uni-hamburg.de TLSA

Verify TLS certificate on primary MX (iplexus1.uke.uni-hamburg.de) RFC 6698

openssl s_client -starttls smtp -connect iplexus1.uke.uni-hamburg.de:25 -servername iplexus1.uke.uni-hamburg.de 2>/dev/null | openssl x509 -noout -subject -dates

Check MTA-STS DNS record RFC 8461

dig +short _mta-sts.uke.de TXT

Fetch MTA-STS policy file RFC 8461

curl -sL https://mta-sts.uke.de/.well-known/mta-sts.txt

Check TLS-RPT record RFC 8460

dig +short _smtp._tls.uke.de TXT

Brand & Trust

Check BIMI record BIMI Draft

dig +short default._bimi.uke.de TXT

Check CAA records (certificate authority authorization) RFC 8659

dig +noall +answer uke.de CAA

DNS Records

Check HTTPS/SVCB records RFC 9460

dig +noall +answer uke.de HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344

dig +noall +answer uke.de CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083

curl -sL 'https://rdap.org/domain/uke.de' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (iplexus1.uke.uni-hamburg.de) RFC 3207

openssl s_client -starttls smtp -connect iplexus1.uke.uni-hamburg.de:25 -servername iplexus1.uke.uni-hamburg.de </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962

curl -s 'https://crt.sh/?q=%25.uke.de&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20

Check security.txt RFC 9116

curl -sL https://uke.de/.well-known/security.txt | head -20

AI Surface

Check for llms.txt

curl -sI https://uke.de/llms.txt | head -5

Check robots.txt for AI crawler rules

curl -s https://uke.de/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 134.100.186.245 (Team Cymru)

dig +short 245.186.100.134.origin.asn.cymru.com TXT

Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.

Intelligence Confidence Audit Engine verified · 9/9 Evaluated

How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.

SPF

Verified 4849 runs

DKIM

Verified 4668 runs

DMARC

Verified 4833 runs

DANE/TLSA

Verified 4652 runs

DNSSEC

Verified 4830 runs

BIMI

Verified 4667 runs

MTA-STS

Verified 4670 runs

TLS-RPT

Verified 4672 runs

CAA

Verified 4664 runs

Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

Query A records (IPv4) (RFC 1035)

dig +noall +answer uke.de A

Query AAAA records (IPv6) (RFC 1035)

dig +noall +answer uke.de AAAA

Query MX records (mail servers) (RFC 1035)

dig +noall +answer uke.de MX

Query NS records (nameservers) (RFC 1035)

dig +noall +answer uke.de NS

Query TXT records (RFC 1035)

dig +noall +answer uke.de TXT

Email Authentication

Check SPF record (RFC 7208)

dig +short uke.de TXT | grep -i spf

Check DMARC policy (RFC 7489)

dig +short _dmarc.uke.de TXT

Check DKIM key for selector 'default' (RFC 6376)

dig +short default._domainkey.uke.de TXT

Check DKIM key for selector 'google' (RFC 6376)

dig +short google._domainkey.uke.de TXT

Check DKIM key for selector 'selector1' (RFC 6376)

dig +short selector1._domainkey.uke.de TXT

Check DKIM key for selector 'selector2' (RFC 6376)

dig +short selector2._domainkey.uke.de TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035)

dig +dnssec +noall +answer uke.de DNSKEY

Check DNSSEC DS records (RFC 4035)

dig +noall +answer uke.de DS

Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035)

dig +dnssec +cd uke.de A @1.1.1.1

Transport Security

Check TLSA record for iplexus1.uke.uni-hamburg.de (RFC 7672)

dig +noall +answer _25._tcp.iplexus1.uke.uni-hamburg.de TLSA

Check TLSA record for iplexus2.uke.uni-hamburg.de (RFC 7672)

dig +noall +answer _25._tcp.iplexus2.uke.uni-hamburg.de TLSA

Verify TLS certificate on primary MX (iplexus1.uke.uni-hamburg.de) (RFC 6698)

openssl s_client -starttls smtp -connect iplexus1.uke.uni-hamburg.de:25 -servername iplexus1.uke.uni-hamburg.de 2>/dev/null | openssl x509 -noout -subject -dates

Check MTA-STS DNS record (RFC 8461)

dig +short _mta-sts.uke.de TXT

Fetch MTA-STS policy file (RFC 8461)

curl -sL https://mta-sts.uke.de/.well-known/mta-sts.txt

Check TLS-RPT record (RFC 8460)

dig +short _smtp._tls.uke.de TXT

Brand & Trust

Check BIMI record (BIMI Draft)

dig +short default._bimi.uke.de TXT

Check CAA records (certificate authority authorization) (RFC 8659)

dig +noall +answer uke.de CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460)

dig +noall +answer uke.de HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344)

dig +noall +answer uke.de CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083)

curl -sL 'https://rdap.org/domain/uke.de' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (iplexus1.uke.uni-hamburg.de) (RFC 3207)

openssl s_client -starttls smtp -connect iplexus1.uke.uni-hamburg.de:25 -servername iplexus1.uke.uni-hamburg.de </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962)

curl -s 'https://crt.sh/?q=%25.uke.de&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20

Check security.txt (RFC 9116)

curl -sL https://uke.de/.well-known/security.txt | head -20

AI Surface

Check for llms.txt

curl -sI https://uke.de/llms.txt | head -5

Check robots.txt for AI crawler rules

curl -s https://uke.de/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 134.100.186.245 (Team Cymru)

dig +short 245.186.100.134.origin.asn.cymru.com TXT

Engineer's DNS Intelligence Report

Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No

Brand Security Can this brand be convincingly faked? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Partial RFC 9116

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? Yes

llms.txt llmstxt.org

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Content-Usage Directive IETF Draft

AI Recommendation Poisoning

Hidden Prompt Artifacts

Evidence Log (3 items)

Public Exposure Checks Are sensitive files or secrets exposed? No

DNS Server Security Hardened

Delegation Consistency 1 Issue

Nameserver Fleet Matrix Healthy

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

Policy Assessment Primary

Telemetry

Live Probe Supplementary

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

Traffic & Routing Where does this domain's traffic actually terminate?

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 491 subdomains discovered

DNS Evidence Diff Side-by-side comparison

DNS History Timeline BETA

Intelligence Sources

Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

Download & Verify Intelligence SHA-3-512

Reproduce the Evidence Transparency Source-Verifiable

Appendix: Verification Commands

Rules of Engagement

What You May Do

What You May Not Do

Engineer's DNS Intelligence Report

Intelligence Dissemination

Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No

Brand Security Can this brand be convincingly faked? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and CAA restricts certificate issuance (RFC 8659 §4), but no BIMI brand verification — lookalike domains display identically in inboxes without visual proof of authenticity

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Partial RFC 9116

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? Yes

llms.txt llmstxt.org

AI Crawler Governance (robots.txt) RFC 9309 IETF Draft

Content-Usage Directive IETF Draft

AI Recommendation Poisoning

Hidden Prompt Artifacts

Evidence Log (3 items)

Public Exposure Checks Are sensitive files or secrets exposed? No

DNS Server Security Hardened

Delegation Consistency 1 Issue

Nameserver Fleet Matrix Healthy

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

Policy Assessment Primary

Telemetry

Live Probe Supplementary

Infrastructure Intelligence Who hosts this domain and what services power it? Direct

Domain Security Methodology Can DNS responses be tampered with in transit? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

Traffic & Routing Where does this domain's traffic actually terminate?

Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 491 subdomains discovered

DNS Evidence Diff Side-by-side comparison

DNS History Timeline BETA

Intelligence Sources

Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

Download & Verify Intelligence SHA-3-512

Reproduce the Evidence Transparency Source-Verifiable

Appendix: Verification Commands

RFC Reference