DNS Tool

Engineer's DNS Intelligence Report

Generated 10 Mar 2026, 08:58 UTC
Duration 60.0s
Version v26.35.35
Integrity e7fb2067fc44d076867f8219bdd9789faabaf7b43bf72a50a8a440d1cb06d669154c62021b9e84463aa49a4dab464abbf0f643c2cabe54adc08f2d3ff26e2fec

TLP:AMBER

Limited disclosure — recipients may share within their organization only

Subject Domain

surland.de

Engineer's DNS Intelligence Report

surland.de

10 Mar 2026, 08:58 UTC · 60.0s ·v26.35.35 · SHA-3-512: e7fb✱✱✱✱ Verify

Executive Methodology

Recon Mode Snapshot Re-analyze New Domain

Footprint 1 SaaS Service

DNS Security & Trust Posture

Risk Level: Low Risk

3 protocols configured, 6 not configured Domain appears to be in deliberate DMARC deployment phase — quarantine fully enforced with reporting, consider upgrading to reject Why we go beyond letter grades

1 recommendation 1 monitoring

Analysis Confidence (ICD 203)

MODERATE 73/100

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

Accuracy 63% Currency 85/100 Maturity verified

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

Intelligence Currency

Data Currency: Good 85/100

ICuAE Details

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

DNS data is mostly current with minor gaps — good intelligence currency

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
NS	`1 hour (3600s)`	`1 day (86400s)`	high	NS TTL is below typical — observed 1 hour (3600s), 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-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.

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 surland.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 root-dns.netcup.net

Serial 2024101826

Admin dnsadmin.netcup.net

Provider Unknown

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

All SOA timer values are within RFC 1912 recommended ranges.

Suggested Scanner Configuration High Confidence

Based on 14 historical scans of this domain

Parameter	Current	Suggested	Severity	Rationale
timeout_seconds	`5s`	`8s`	low	Average scan duration is 43.3s, suggesting DNS responses are slow for this domain. Increasing timeout from 5s to 8s prevents premature resolution failures. RFC 8767

Suggestions require explicit approval before applying. No automatic changes will be made.

Email Spoofing

Protected

Brand Impersonation

Not Setup

DNS Tampering

Unsigned

Certificate Control

Open

Recommended

Upgrade DMARC policy from quarantine to reject (p=reject) for maximum spoofing protection

Monitoring

External domain michels-marc.de has not authorized surland.de to send DMARC reports (missing surland.de._report._dmarc.michels-marc.de TXT record)

Configured

SPF, DMARC (quarantine, 100%), DKIM

Not Configured

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

Priority Actions 5 total Achievable posture: Secure

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

Medium Upgrade DMARC to Reject

Your DMARC policy is set to quarantine. Upgrade to p=reject for maximum protection — reject instructs receivers to discard spoofed mail entirely rather than quarantining it.

A reject policy provides the strongest protection against domain spoofing.

Field	Value
Type	`TXT`
Host	`_dmarc.surland.de` (update existing DMARC record)
Value	`v=DMARC1; p=reject; rua=mailto:dmarc-reports@surland.de`

RFC 7489 §6.3

Low Add CAA Records

CAA records specify which Certificate Authorities may issue certificates for your domain, reducing the risk of unauthorized certificate issuance.

CAA constrains which CAs can issue certificates for this domain.

Field	Value
Type	`CAA`
Host	`surland.de` (root of domain — adjust CA to match your provider)
Value	`0 issue "letsencrypt.org"`

RFC 8659

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.surland.de` (SMTP TLS reporting record)
Value	`v=TLSRPTv1; rua=mailto:tls-reports@surland.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.surland.de` (MTA-STS policy record)
Value	`v=STSv1; id=surland.de`

RFC 8461

Registrar (RDAP) LIVE

Unknown

Where domain was purchased

Email Service Provider

Unknown

Moderately 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? Unlikely SPF and DMARC quarantine policy enforced

SPF Record RFC 7208 §4 Verified

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

Success ~all 3/10 lookups

SPF valid with industry-standard soft fail (~all), 3/10 lookups

v=spf1 mx a include:servers.mcsv.net ~all

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)

~all is the industry standard. Google, Apple, and most providers default to soft fail. CISA (BOD 18-01) and RFC 7489 confirm that DMARC policy — not SPF alone — is the primary enforcement control. Using ~all allows DKIM to be evaluated before a DMARC decision is made. This domain uses ~all + DMARC quarantine — good protection. Moving to p=reject would achieve the strongest stance.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Quarantined, not rejected

Success p=quarantine

DMARC policy quarantine (100%) - good protection

v=DMARC1;p=quarantine;sp=quarantine;pct=100;rua=mailto:post@michels-marc.de;ruf=mailto:post@michels-marc.de;ri=86400;fo=1;

Alignment: SPF relaxed DKIM relaxed sp=quarantine

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

Advanced cryptographic posture detected. Domain appears to be in deliberate DMARC deployment phase — quarantine fully enforced with reporting, consider upgrading to reject

RFC 7489 Present — DMARC record published per RFC 7489 §6.3.

Monitoring Posture Note: Quarantine sequesters authentication failures while preserving full DMARC forensic telemetry (RFC 7489 §7). Some organizations maintain quarantine rather than reject as a deliberate monitoring strategy — failed messages are processed and reported but sequestered from the inbox. See NIST SP 800-177 Rev. 1 for enforcement tradeoffs.

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? Yes — verified

Found 2048-bit

Found DKIM for 3 selector(s) with strong keys (2048-bit)

k1._domainkey 2048-bit Adequate

k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;

key1._domainkey 2048-bit Adequate

v=DKIM1; h=sha256; k=rsa; s=email; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3iZ3AlDj02zi0d54fFD7GNgDjlhLlBlRFP1B2/By6dwp4WRbCvY0cudVUZFJSH3oVrPucK159IYwSR98EvyXM3Gc63LeQl3XK7+B5GgLnP+DBHWDxIJBxaFGLzURpykCbXDuJ8QaS+AknhWnNP5f7KIwroevQO8+banQljw8isXO52Nv+HPeBQN63+pJC3vfDQeiipBoMLlAsRG5R73AddT1RDlL2EKm1MREqTEkZ/tBh6VIGPzxOCr/jKWsqeY5/saNqkplI1B2UeoPmrVUo2PE7uEfB8OLBYurjAVhDisTI+0zOssGousQdjxqs2/qMUhA9gR3EwnAHqY7ZhFP/wIDAQAB

key2._domainkey 2048-bit Adequate

v=DKIM1; h=sha256; k=rsa; s=email; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmFTQ2W4oTdiCzU6HLIVO101ba5RhC3+5GMq7sxuO8AbHyKaFriIDaiQg1X+GGF711KF3s67t8QyVvMgiDpO5GpJjW1UG4Wgk92D0uiIoSVjZzfVDp6GVeNj5UCFzTISU8NupArEaYjQNcmjZ9Ln+kqszw42mUYey2J5DVBccoRXEl2Fum51cNdL0AHhDC/XTZsWUEKCs8HV3rLjV7G3f4+F7pb8UnAwkQrRRSWkBDzrAXHq2u7ojFmLmM0k4JT09TSthjuRQHwK9GZIb7z56N4TOYWjdgxPnSLXT9EAzOwRr/hiL0E6N0alwIDIMR1FpjYC5jrHkckU0fL3e7tV4IQIDAQAB

RFC 6376 Conformant — DKIM keys and signatures conform to RFC 6376 §3.6 (Internet Standard).

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

DMARC External Reporting Authorization RFC 7489 §7.1

Are external report receivers authorized? Authorization missing

Warning

1 of 1 external reporting domains missing authorization

External Domain	Authorization	Auth Record
`michels-marc.de`	Unauthorized	—

External domain michels-marc.de has not authorized surland.de to send DMARC reports (missing surland.de._report._dmarc.michels-marc.de TXT record)

Third-Party Action Required

This authorization record must be created by the external reporting provider, not by you. Per RFC 7489 §7.1, the receiving domain must publish a TXT record to confirm it accepts DMARC reports from your domain.

What to do: Contact your DMARC reporting provider and ask them to publish the authorization TXT record shown above. If you use a managed DMARC service (e.g., Ondmarc, Dmarcian, Valimail), this is typically handled during onboarding — reach out to their support if the record is missing.

Impact if unresolved: Compliant receivers may silently discard aggregate or forensic reports destined for the unauthorized address, reducing your DMARC visibility.

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? Likely DMARC quarantine flags but does not reject spoofed mail (RFC 7489 §6.3) — no BIMI or CAA (RFC 8659) reinforcement leaves brand impersonation largely unaddressed

BIMI BIMI Spec Verified Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Verified Warning

Does this domain restrict who can issue TLS certificates? No

No CAA records found - any CA can issue certificates

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

No security.txt found

A security.txt file at /.well-known/security.txt provides security researchers with a standardized way to report vulnerabilities. See securitytxt.org for a generator.

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

No AI governance measures detected

llms.txt llmstxt.org

Is this domain publishing AI-readable brand context? No

No llms.txt found

No llms-full.txt found

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 (1 item)

Type	Detail	Severity	Confidence
`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.

Sources scanned (9)

http://surland.de/
https://surland.de/wp-includes/js/jquery/jquery.min.js?ver=3.7.1
https://surland.de/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1
https://surland.de/wp-content/plugins/to-top/public/js/to-top-public.js?ver=2.5.5
https://surland.de/wp-content/plugins/woo-coupon-url/public/js/woo-coupon-url-public.js?ver=1.0.0
https://surland.de/wp-content/plugins/woocommerce/assets/js/jquery-blockui/jquery.blockUI.min.js?ver=2.7.0-wc.10.3.8
https://surland.de/wp-content/plugins/woocommerce/assets/js/frontend/add-to-cart.min.js?ver=10.3.8
https://surland.de/wp-content/plugins/woocommerce/assets/js/js-cookie/js.cookie.min.js?ver=2.1.4-wc.10.3.8
https://surland.de/wp-content/plugins/woocommerce/assets/js/frontend/woocommerce.min.js?ver=10.3.8

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 second-dns.netcup.net — 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: second-dns.netcup.net, root-dns.netcup.net, third-dns.netcup.net

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
`root-dns.netcup.net`	No	N/A	N/A	OK
`second-dns.netcup.net`	No	N/A	N/A	OK
`third-dns.netcup.net`	No	N/A	N/A	OK

NS TTL Comparison Drift

Child TTL: 3600s Drift: 0s

SOA Serial Consistency Consistent

root-dns.netcup.net: 2.024101826e+09

second-dns.netcup.net: 2.024101826e+09

third-dns.netcup.net: 2.024101826e+09

Nameserver Fleet Matrix 2 Issues

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

Findings:

second-dns.netcup.net: TCP unreachable on port 53
third-dns.netcup.net: TCP unreachable on port 53

Nameserver	IPv4	IPv6	ASN / Operator	SOA Serial
`second-dns.netcup.net`	37.221.199.199	2a03:4000:2:24b::c7c7	AS197540 Netcup GmbH	2024101826
`third-dns.netcup.net`	188.68.63.68	2a03:4001:0:106::3f44	AS197540 Netcup GmbH	2024101826
`root-dns.netcup.net`	46.38.225.225	2a03:4000:0:1::e1e1	AS197540 Netcup GmbH	2024101826

Unique ASNs

Unique Operators

Unique /24 Prefixes

Diversity Score

Fair

1 ASN(s), 3 /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

No transport encryption policy detected — mail delivery relies on opportunistic TLS

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

Skipped — Remote probe failed (connection failed — probe may be offline) and local port 25 is blocked. Transport security is assessed via DNS policy records per NIST SP 800-177 Rev. 1.

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

ASN / Network Success

Resolved 0 unique ASN(s) across 2 IP address(es)

IPv4 Mappings:

188.68.47.111 → AS ()

IPv6 Mappings:

2a03:4000:30:3c1d::11:5469 → AS ()

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=X0k8_LYp6P9s4lEqRiP9e62J-f1U11uPoaS9IehL3XY`

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

3 nameserver(s) configured

Nameservers: root-dns.netcup.net second-dns.netcup.net third-dns.netcup.net

Multi-Resolver Verification Recon: Consensus reached - 5 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records

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

AIPv4 Address

188.68.47.111

Where the domain points for web traffic

AAAAIPv6 Address

2a03:4000:30:3c1d::11:5469

IPv6 ready

MXMail Servers

10 mail.surland.de.

50 mx2f71.netcup.net.

Priority + mail server for email delivery

SRVServices

No SRV records

No service-specific routing configured

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

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

How did we find these?

4 unique certificates 488 current 0 expired 1 CNAME Source: Certificate Transparency + DNS Intelligence

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

Certificate Authority Diversity (1 CA observed across CT log history)

Certificate Authority	Certs	First Issued	Last Issued	Status
`Let's Encrypt`	4	2025-12-11	2026-02-13	Active

Subdomain	Source	Status	Provider / CNAME	Certificates	First Seen	Issuer(s)
`a.surland.de`	DNS	Current	—	—	—	—
`academy.surland.de`	DNS	Current	—	—	—	—
`account.surland.de`	DNS	Current	—	—	—	—
`accounting.surland.de`	DNS	Current	—	—	—	—
`accounts.surland.de`	DNS	Current	—	—	—	—
`ad.surland.de`	DNS	Current	—	—	—	—
`adfs.surland.de`	DNS	Current	—	—	—	—
`admin.surland.de`	DNS	Current	—	—	—	—
`admin1.surland.de`	DNS	Current	—	—	—	—
`admin2.surland.de`	DNS	Current	—	—	—	—
`alert.surland.de`	DNS	Current	—	—	—	—
`alerts.surland.de`	DNS	Current	—	—	—	—
`alpha.surland.de`	DNS	Current	—	—	—	—
`analytics.surland.de`	DNS	Current	—	—	—	—
`ap-south.surland.de`	DNS	Current	—	—	—	—
`ap.surland.de`	DNS	Current	—	—	—	—
`apac.surland.de`	DNS	Current	—	—	—	—
`api.surland.de`	DNS	Current	—	—	—	—
`api1.surland.de`	DNS	Current	—	—	—	—
`api2.surland.de`	DNS	Current	—	—	—	—
`api3.surland.de`	DNS	Current	—	—	—	—
`apigw.surland.de`	DNS	Current	—	—	—	—
`apis.surland.de`	DNS	Current	—	—	—	—
`apm.surland.de`	DNS	Current	—	—	—	—
`app.surland.de`	DNS	Current	—	—	—	—
`app1.surland.de`	DNS	Current	—	—	—	—
`app2.surland.de`	DNS	Current	—	—	—	—
`appointments.surland.de`	DNS	Current	—	—	—	—
`apps.surland.de`	DNS	Current	—	—	—	—
`archive.surland.de`	DNS	Current	—	—	—	—
`archives.surland.de`	DNS	Current	—	—	—	—
`asia.surland.de`	DNS	Current	—	—	—	—
`assets.surland.de` 80/tcp nginx 443/tcp nginx	DNS	Current	—	—	—	—
`atom.surland.de`	DNS	Current	—	—	—	—
`auth.surland.de`	DNS	Current	—	—	—	—
`auth0.surland.de`	DNS	Current	—	—	—	—
`autoconfig.surland.de`	DNS	Current	`autoconfig.netcup.net`	—	—	—
`autodiscover.surland.de`	DNS	Current	—	—	—	—
`b.surland.de`	DNS	Current	—	—	—	—
`backup.surland.de`	DNS	Current	—	—	—	—
`backup1.surland.de`	DNS	Current	—	—	—	—
`backup2.surland.de`	DNS	Current	—	—	—	—
`beta.surland.de`	DNS	Current	—	—	—	—
`bi.surland.de`	DNS	Current	—	—	—	—
`bigdata.surland.de`	DNS	Current	—	—	—	—
`billing.surland.de`	DNS	Current	—	—	—	—
`bitbucket.surland.de`	DNS	Current	—	—	—	—
`blob.surland.de`	DNS	Current	—	—	—	—
`blog.surland.de`	DNS	Current	—	—	—	—
`booking.surland.de`	DNS	Current	—	—	—	—
`broker.surland.de`	DNS	Current	—	—	—	—
`bucket.surland.de`	DNS	Current	—	—	—	—
`build.surland.de`	DNS	Current	—	—	—	—
`builds.surland.de`	DNS	Current	—	—	—	—
`c.surland.de`	DNS	Current	—	—	—	—
`ca.surland.de`	DNS	Current	—	—	—	—
`cache.surland.de`	DNS	Current	—	—	—	—
`cal.surland.de`	DNS	Current	—	—	—	—
`calendar.surland.de`	DNS	Current	—	—	—	—
`campaign.surland.de`	DNS	Current	—	—	—	—
`campaigns.surland.de`	DNS	Current	—	—	—	—
`careers.surland.de`	DNS	Current	—	—	—	—
`cart.surland.de`	DNS	Current	—	—	—	—
`catalog.surland.de`	DNS	Current	—	—	—	—
`cd.surland.de`	DNS	Current	—	—	—	—
`cdn.surland.de`	DNS	Current	—	—	—	—
`cdn1.surland.de`	DNS	Current	—	—	—	—
`cdn2.surland.de`	DNS	Current	—	—	—	—
`cdn3.surland.de`	DNS	Current	—	—	—	—
`cert.surland.de`	DNS	Current	—	—	—	—
`certs.surland.de`	DNS	Current	—	—	—	—
`chat.surland.de`	DNS	Current	—	—	—	—
`checkout.surland.de`	DNS	Current	—	—	—	—
`ci.surland.de`	DNS	Current	—	—	—	—
`client.surland.de`	DNS	Current	—	—	—	—
`clients.surland.de`	DNS	Current	—	—	—	—
`cloud.surland.de`	DNS	Current	—	—	—	—
`cms.surland.de`	DNS	Current	—	—	—	—
`cname.surland.de`	DNS	Current	—	—	—	—
`code.surland.de`	DNS	Current	—	—	—	—
`community.surland.de`	DNS	Current	—	—	—	—
`compliance.surland.de`	DNS	Current	—	—	—	—
`conference.surland.de`	DNS	Current	—	—	—	—
`config.surland.de`	DNS	Current	—	—	—	—
`configuration.surland.de`	DNS	Current	—	—	—	—
`confluence.surland.de` 80/tcp nginx 443/tcp nginx	DNS	Current	—	—	—	—
`connect.surland.de`	DNS	Current	—	—	—	—
`console.surland.de`	DNS	Current	—	—	—	—
`containers.surland.de`	DNS	Current	—	—	—	—
`content.surland.de`	DNS	Current	—	—	—	—
`corp.surland.de`	DNS	Current	—	—	—	—
`corporate.surland.de`	DNS	Current	—	—	—	—
`courses.surland.de`	DNS	Current	—	—	—	—
`cpanel.surland.de`	DNS	Current	—	—	—	—
`crl.surland.de`	DNS	Current	—	—	—	—
`crm.surland.de`	DNS	Current	—	—	—	—
`d.surland.de`	DNS	Current	—	—	—	—
`dashboard.surland.de`	DNS	Current	—	—	—	—
`data.surland.de`	DNS	Current	—	—	—	—
`data1.surland.de`	DNS	Current	—	—	—	—
`data2.surland.de`	DNS	Current	—	—	—	—
`database.surland.de`	DNS	Current	—	—	—	—
`datadog.surland.de`	DNS	Current	—	—	—	—
`db.surland.de`	DNS	Current	—	—	—	—
`db1.surland.de`	DNS	Current	—	—	—	—
`db2.surland.de`	DNS	Current	—	—	—	—
`dedicated.surland.de`	DNS	Current	—	—	—	—
`demo.surland.de`	DNS	Current	—	—	—	—
`deploy.surland.de`	DNS	Current	—	—	—	—
`deployment.surland.de`	DNS	Current	—	—	—	—
`dev.surland.de`	DNS	Current	—	—	—	—
`dev1.surland.de`	CT Log	Current	—	2	2026-01-19T23:18:44	Let's Encrypt
`dev2.surland.de`	DNS	Current	—	—	—	—
`develop.surland.de`	DNS	Current	—	—	—	—
`developer.surland.de`	DNS	Current	—	—	—	—
`developers.surland.de`	DNS	Current	—	—	—	—
`devices.surland.de`	DNS	Current	—	—	—	—
`directory.surland.de`	DNS	Current	—	—	—	—
`discuss.surland.de`	DNS	Current	—	—	—	—
`discussions.surland.de`	DNS	Current	—	—	—	—
`dns.surland.de`	DNS	Current	—	—	—	—
`dns1.surland.de`	DNS	Current	—	—	—	—
`dns2.surland.de`	DNS	Current	—	—	—	—
`doc.surland.de`	DNS	Current	—	—	—	—
`docker.surland.de`	DNS	Current	—	—	—	—
`docs.surland.de`	DNS	Current	—	—	—	—
`documentation.surland.de`	DNS	Current	—	—	—	—
`download.surland.de`	DNS	Current	—	—	—	—
`downloads.surland.de`	DNS	Current	—	—	—	—
`drupal.surland.de`	DNS	Current	—	—	—	—
`e.surland.de`	DNS	Current	—	—	—	—
`ecommerce.surland.de`	DNS	Current	—	—	—	—
`edge.surland.de`	DNS	Current	—	—	—	—
`edge1.surland.de`	DNS	Current	—	—	—	—
`edge2.surland.de`	DNS	Current	—	—	—	—
`education.surland.de`	DNS	Current	—	—	—	—
`elastic.surland.de`	DNS	Current	—	—	—	—
`elasticsearch.surland.de`	DNS	Current	—	—	—	—
`email.surland.de`	DNS	Current	—	—	—	—
`emea.surland.de`	DNS	Current	—	—	—	—
`endpoint.surland.de`	DNS	Current	—	—	—	—
`erp.surland.de`	DNS	Current	—	—	—	—
`es.surland.de`	DNS	Current	—	—	—	—
`etl.surland.de`	DNS	Current	—	—	—	—
`eu-west.surland.de`	DNS	Current	—	—	—	—
`eu.surland.de`	DNS	Current	—	—	—	—
`event.surland.de`	DNS	Current	—	—	—	—
`events.surland.de`	DNS	Current	—	—	—	—
`exchange.surland.de`	DNS	Current	—	—	—	—
`ext.surland.de`	DNS	Current	—	—	—	—
`f.surland.de`	DNS	Current	—	—	—	—
`faq.surland.de`	DNS	Current	—	—	—	—
`feed.surland.de`	DNS	Current	—	—	—	—
`feedback.surland.de`	DNS	Current	—	—	—	—
`feeds.surland.de`	DNS	Current	—	—	—	—
`file.surland.de`	DNS	Current	—	—	—	—
`files.surland.de`	DNS	Current	—	—	—	—
`finance.surland.de`	DNS	Current	—	—	—	—
`firewall.surland.de`	DNS	Current	—	—	—	—
`forms.surland.de`	DNS	Current	—	—	—	—
`forum.surland.de`	DNS	Current	—	—	—	—
`forums.surland.de`	DNS	Current	—	—	—	—
`ftp.surland.de`	DNS	Current	—	—	—	—
`ftp1.surland.de`	DNS	Current	—	—	—	—
`ftp2.surland.de`	DNS	Current	—	—	—	—
`fw.surland.de`	DNS	Current	—	—	—	—
`gateway.surland.de`	DNS	Current	—	—	—	—
`geo.surland.de`	DNS	Current	—	—	—	—
`gis.surland.de`	DNS	Current	—	—	—	—
`git.surland.de`	DNS	Current	—	—	—	—
`github.surland.de`	DNS	Current	—	—	—	—
`gitlab.surland.de`	DNS	Current	—	—	—	—
`go.surland.de`	DNS	Current	—	—	—	—
`grafana.surland.de`	DNS	Current	—	—	—	—
`graphql.surland.de`	DNS	Current	—	—	—	—
`gw.surland.de`	DNS	Current	—	—	—	—
`gw1.surland.de`	DNS	Current	—	—	—	—
`gw2.surland.de`	DNS	Current	—	—	—	—
`haproxy.surland.de`	DNS	Current	—	—	—	—
`health.surland.de`	DNS	Current	—	—	—	—
`healthcheck.surland.de`	DNS	Current	—	—	—	—
`help.surland.de`	DNS	Current	—	—	—	—
`helpdesk.surland.de`	DNS	Current	—	—	—	—
`hiring.surland.de`	DNS	Current	—	—	—	—
`host.surland.de`	DNS	Current	—	—	—	—
`hosting.surland.de`	DNS	Current	—	—	—	—
`hq.surland.de`	DNS	Current	—	—	—	—
`hr.surland.de`	DNS	Current	—	—	—	—
`hris.surland.de`	DNS	Current	—	—	—	—
`hub.surland.de`	DNS	Current	—	—	—	—
`id.surland.de`	DNS	Current	—	—	—	—
`identity.surland.de`	DNS	Current	—	—	—	—
`image.surland.de`	DNS	Current	—	—	—	—
`images.surland.de`	DNS	Current	—	—	—	—
`imap.surland.de`	DNS	Current	—	—	—	—
`img.surland.de`	DNS	Current	—	—	—	—
`int.surland.de`	DNS	Current	—	—	—	—
`internal.surland.de`	DNS	Current	—	—	—	—
`intranet.surland.de`	DNS	Current	—	—	—	—
`inventory.surland.de`	DNS	Current	—	—	—	—
`investor.surland.de`	DNS	Current	—	—	—	—
`investors.surland.de`	DNS	Current	—	—	—	—
`invoice.surland.de`	DNS	Current	—	—	—	—
`ir.surland.de`	DNS	Current	—	—	—	—
`it.surland.de`	DNS	Current	—	—	—	—
`itsm.surland.de`	DNS	Current	—	—	—	—
`itsupport.surland.de`	DNS	Current	—	—	—	—
`jenkins.surland.de`	DNS	Current	—	—	—	—
`jira.surland.de`	DNS	Current	—	—	—	—
`jobs.surland.de`	DNS	Current	—	—	—	—
`k8s.surland.de`	DNS	Current	—	—	—	—
`kafka.surland.de`	DNS	Current	—	—	—	—
`kb.surland.de`	DNS	Current	—	—	—	—
`kibana.surland.de`	DNS	Current	—	—	—	—
`kong.surland.de`	DNS	Current	—	—	—	—
`kubernetes.surland.de`	DNS	Current	—	—	—	—
`lab.surland.de`	DNS	Current	—	—	—	—
`labs.surland.de`	DNS	Current	—	—	—	—
`lan.surland.de`	DNS	Current	—	—	—	—
`lb.surland.de`	DNS	Current	—	—	—	—
`ldap.surland.de`	DNS	Current	—	—	—	—
`learn.surland.de`	DNS	Current	—	—	—	—
`learning.surland.de`	DNS	Current	—	—	—	—
`legal.surland.de`	DNS	Current	—	—	—	—
`link.surland.de`	DNS	Current	—	—	—	—
`links.surland.de`	DNS	Current	—	—	—	—
`live.surland.de`	DNS	Current	—	—	—	—
`lms.surland.de`	DNS	Current	—	—	—	—
`loadbalancer.surland.de`	DNS	Current	—	—	—	—
`location.surland.de`	DNS	Current	—	—	—	—
`log.surland.de`	DNS	Current	—	—	—	—
`login.surland.de`	DNS	Current	—	—	—	—
`logs.surland.de`	DNS	Current	—	—	—	—
`m.surland.de`	DNS	Current	—	—	—	—
`mail.surland.de`	DNS	Current	—	—	—	—
`mail1.surland.de` 80/tcp nginx 443/tcp nginx	DNS	Current	—	—	—	—
`mail2.surland.de`	DNS	Current	—	—	—	—
`mail3.surland.de`	DNS	Current	—	—	—	—
`manage.surland.de`	DNS	Current	—	—	—	—
`management.surland.de`	DNS	Current	—	—	—	—
`manager.surland.de`	DNS	Current	—	—	—	—
`map.surland.de`	DNS	Current	—	—	—	—
`maps.surland.de`	DNS	Current	—	—	—	—
`marketing.surland.de`	DNS	Current	—	—	—	—
`mdm.surland.de`	DNS	Current	—	—	—	—
`media.surland.de`	DNS	Current	—	—	—	—
`meet.surland.de`	DNS	Current	—	—	—	—
`meeting.surland.de`	DNS	Current	—	—	—	—
`memcached.surland.de`	DNS	Current	—	—	—	—
`metrics.surland.de`	DNS	Current	—	—	—	—
`microservices.surland.de`	DNS	Current	—	—	—	—
`mobile.surland.de`	DNS	Current	—	—	—	—
`mongo.surland.de`	DNS	Current	—	—	—	—
`mongodb.surland.de`	DNS	Current	—	—	—	—
`monitor.surland.de`	DNS	Current	—	—	—	—
`monitoring.surland.de`	DNS	Current	—	—	—	—
`mq.surland.de`	DNS	Current	—	—	—	—
`mta.surland.de`	DNS	Current	—	—	—	—
`mx.surland.de`	DNS	Current	—	—	—	—
`mx1.surland.de`	DNS	Current	—	—	—	—
`mx2.surland.de`	DNS	Current	—	—	—	—
`mx3.surland.de`	DNS	Current	—	—	—	—
`mx4.surland.de`	DNS	Current	—	—	—	—
`mx5.surland.de`	DNS	Current	—	—	—	—
`my.surland.de`	DNS	Current	—	—	—	—
`myaccount.surland.de`	DNS	Current	—	—	—	—
`mysql.surland.de`	DNS	Current	—	—	—	—
`na.surland.de`	DNS	Current	—	—	—	—
`nagios.surland.de`	DNS	Current	—	—	—	—
`net.surland.de`	DNS	Current	—	—	—	—
`network.surland.de`	DNS	Current	—	—	—	—
`new.surland.de`	CT Log	Current	—	2	2026-02-13T07:45:26	Let's Encrypt
`news.surland.de`	DNS	Current	—	—	—	—
`nginx.surland.de`	DNS	Current	—	—	—	—
`node1.surland.de`	DNS	Current	—	—	—	—
`node2.surland.de`	DNS	Current	—	—	—	—
`node3.surland.de`	DNS	Current	—	—	—	—
`notifications.surland.de`	DNS	Current	—	—	—	—
`notify.surland.de`	DNS	Current	—	—	—	—
`ns.surland.de`	DNS	Current	—	—	—	—
`ns1.surland.de`	DNS	Current	—	—	—	—
`ns2.surland.de`	DNS	Current	—	—	—	—
`ns3.surland.de`	DNS	Current	—	—	—	—
`ns4.surland.de`	DNS	Current	—	—	—	—
`ns5.surland.de`	DNS	Current	—	—	—	—
`ns6.surland.de`	DNS	Current	—	—	—	—
`o365.surland.de`	DNS	Current	—	—	—	—
`oauth.surland.de`	DNS	Current	—	—	—	—
`object.surland.de`	DNS	Current	—	—	—	—
`ocsp.surland.de`	DNS	Current	—	—	—	—
`office.surland.de`	DNS	Current	—	—	—	—
`okta.surland.de`	DNS	Current	—	—	—	—
`order.surland.de`	DNS	Current	—	—	—	—
`orders.surland.de`	DNS	Current	—	—	—	—
`origin.surland.de`	DNS	Current	—	—	—	—
`origin1.surland.de`	DNS	Current	—	—	—	—
`origin2.surland.de`	DNS	Current	—	—	—	—
`outlook.surland.de`	DNS	Current	—	—	—	—
`owa.surland.de`	DNS	Current	—	—	—	—
`panel.surland.de`	DNS	Current	—	—	—	—
`partner.surland.de`	DNS	Current	—	—	—	—
`partners.surland.de`	DNS	Current	—	—	—	—
`pay.surland.de`	DNS	Current	—	—	—	—
`payment.surland.de`	DNS	Current	—	—	—	—
`payments.surland.de`	DNS	Current	—	—	—	—
`payroll.surland.de`	DNS	Current	—	—	—	—
`pbx.surland.de`	DNS	Current	—	—	—	—
`phone.surland.de`	DNS	Current	—	—	—	—
`photos.surland.de`	DNS	Current	—	—	—	—
`pki.surland.de`	DNS	Current	—	—	—	—
`plesk.surland.de`	DNS	Current	—	—	—	—
`policies.surland.de`	DNS	Current	—	—	—	—
`policy.surland.de`	DNS	Current	—	—	—	—
`pop.surland.de`	DNS	Current	—	—	—	—
`pop3.surland.de`	DNS	Current	—	—	—	—
`portal.surland.de`	DNS	Current	—	—	—	—
`portal2.surland.de`	DNS	Current	—	—	—	—
`postgres.surland.de`	DNS	Current	—	—	—	—
`pre.surland.de`	DNS	Current	—	—	—	—
`preprod.surland.de`	DNS	Current	—	—	—	—
`press.surland.de`	DNS	Current	—	—	—	—
`preview.surland.de`	DNS	Current	—	—	—	—
`primary.surland.de`	DNS	Current	—	—	—	—
`print.surland.de`	DNS	Current	—	—	—	—
`printer.surland.de`	DNS	Current	—	—	—	—
`privacy.surland.de`	DNS	Current	—	—	—	—
`private.surland.de`	DNS	Current	—	—	—	—
`product.surland.de`	DNS	Current	—	—	—	—
`products.surland.de`	DNS	Current	—	—	—	—
`profile.surland.de`	DNS	Current	—	—	—	—
`prometheus.surland.de`	DNS	Current	—	—	—	—
`promo.surland.de`	DNS	Current	—	—	—	—
`proxy.surland.de`	DNS	Current	—	—	—	—
`proxy1.surland.de`	DNS	Current	—	—	—	—
`proxy2.surland.de`	DNS	Current	—	—	—	—
`public.surland.de`	DNS	Current	—	—	—	—
`qa.surland.de`	DNS	Current	—	—	—	—
`queue.surland.de`	DNS	Current	—	—	—	—
`r.surland.de`	DNS	Current	—	—	—	—
`ra.surland.de`	DNS	Current	—	—	—	—
`rabbitmq.surland.de`	DNS	Current	—	—	—	—
`rancher.surland.de`	DNS	Current	—	—	—	—
`realtime.surland.de`	DNS	Current	—	—	—	—
`recruit.surland.de`	DNS	Current	—	—	—	—
`redirect.surland.de`	DNS	Current	—	—	—	—
`redis.surland.de`	DNS	Current	—	—	—	—
`register.surland.de`	DNS	Current	—	—	—	—
`registry.surland.de`	DNS	Current	—	—	—	—
`relay.surland.de`	DNS	Current	—	—	—	—
`relay1.surland.de`	DNS	Current	—	—	—	—
`releases.surland.de`	DNS	Current	—	—	—	—
`remote.surland.de`	DNS	Current	—	—	—	—
`repo.surland.de`	DNS	Current	—	—	—	—
`report.surland.de`	DNS	Current	—	—	—	—
`reporting.surland.de`	DNS	Current	—	—	—	—
`reports.surland.de`	DNS	Current	—	—	—	—
`repos.surland.de`	DNS	Current	—	—	—	—
`reservations.surland.de`	DNS	Current	—	—	—	—
`rest.surland.de`	DNS	Current	—	—	—	—
`rss.surland.de`	DNS	Current	—	—	—	—
`rt.surland.de`	DNS	Current	—	—	—	—
`s3.surland.de`	DNS	Current	—	—	—	—
`sandbox.surland.de`	DNS	Current	—	—	—	—
`sandbox1.surland.de`	DNS	Current	—	—	—	—
`sandbox2.surland.de`	DNS	Current	—	—	—	—
`scan.surland.de`	DNS	Current	—	—	—	—
`scanner.surland.de`	DNS	Current	—	—	—	—
`schedule.surland.de`	DNS	Current	—	—	—	—
`scp.surland.de`	DNS	Current	—	—	—	—
`search.surland.de`	DNS	Current	—	—	—	—
`secondary.surland.de`	DNS	Current	—	—	—	—
`secrets.surland.de`	DNS	Current	—	—	—	—
`secure.surland.de`	DNS	Current	—	—	—	—
`server.surland.de`	DNS	Current	—	—	—	—
`server1.surland.de`	DNS	Current	—	—	—	—
`server2.surland.de`	DNS	Current	—	—	—	—
`server3.surland.de`	DNS	Current	—	—	—	—
`service.surland.de`	DNS	Current	—	—	—	—
`servicedesk.surland.de`	DNS	Current	—	—	—	—
`services.surland.de`	DNS	Current	—	—	—	—
`sftp.surland.de`	DNS	Current	—	—	—	—
`share.surland.de`	DNS	Current	—	—	—	—
`shop.surland.de`	DNS	Current	—	—	—	—
`signin.surland.de`	DNS	Current	—	—	—	—
`signup.surland.de`	DNS	Current	—	—	—	—
`sip.surland.de`	DNS	Current	—	—	—	—
`slack.surland.de`	DNS	Current	—	—	—	—
`smtp.surland.de`	DNS	Current	—	—	—	—
`smtp1.surland.de`	DNS	Current	—	—	—	—
`smtp2.surland.de`	DNS	Current	—	—	—	—
`socket.surland.de`	DNS	Current	—	—	—	—
`solr.surland.de`	DNS	Current	—	—	—	—
`sql.surland.de`	DNS	Current	—	—	—	—
`srv.surland.de`	DNS	Current	—	—	—	—
`srv1.surland.de`	DNS	Current	—	—	—	—
`srv2.surland.de`	DNS	Current	—	—	—	—
`ssh.surland.de`	DNS	Current	—	—	—	—
`ssl.surland.de`	DNS	Current	—	—	—	—
`sso.surland.de`	DNS	Current	—	—	—	—
`stage.surland.de`	DNS	Current	—	—	—	—
`staging.surland.de`	DNS	Current	—	—	—	—
`static.surland.de`	DNS	Current	—	—	—	—
`static1.surland.de`	DNS	Current	—	—	—	—
`static2.surland.de`	DNS	Current	—	—	—	—
`statistics.surland.de`	DNS	Current	—	—	—	—
`stats.surland.de`	DNS	Current	—	—	—	—
`status.surland.de`	DNS	Current	—	—	—	—
`stg.surland.de`	DNS	Current	—	—	—	—
`storage.surland.de`	DNS	Current	—	—	—	—
`store.surland.de`	DNS	Current	—	—	—	—
`stream.surland.de`	DNS	Current	—	—	—	—
`streaming.surland.de`	DNS	Current	—	—	—	—
`support.surland.de`	DNS	Current	—	—	—	—
`support2.surland.de`	DNS	Current	—	—	—	—
`survey.surland.de`	DNS	Current	—	—	—	—
`surveys.surland.de`	DNS	Current	—	—	—	—
`svc.surland.de`	DNS	Current	—	—	—	—
`svn.surland.de`	DNS	Current	—	—	—	—
`swift.surland.de`	DNS	Current	—	—	—	—
`talent.surland.de`	DNS	Current	—	—	—	—
`teams.surland.de`	DNS	Current	—	—	—	—
`techsupport.surland.de`	DNS	Current	—	—	—	—
`tel.surland.de`	DNS	Current	—	—	—	—
`telecom.surland.de`	DNS	Current	—	—	—	—
`terms.surland.de`	DNS	Current	—	—	—	—
`test.surland.de`	DNS	Current	—	—	—	—
`test1.surland.de`	DNS	Current	—	—	—	—
`test2.surland.de`	DNS	Current	—	—	—	—
`testing.surland.de`	DNS	Current	—	—	—	—
`ticket.surland.de`	DNS	Current	—	—	—	—
`tickets.surland.de`	DNS	Current	—	—	—	—
`tls.surland.de`	DNS	Current	—	—	—	—
`tool.surland.de`	DNS	Current	—	—	—	—
`tools.surland.de`	DNS	Current	—	—	—	—
`trace.surland.de`	DNS	Current	—	—	—	—
`tracing.surland.de`	DNS	Current	—	—	—	—
`tracking.surland.de`	DNS	Current	—	—	—	—
`training.surland.de`	DNS	Current	—	—	—	—
`uat.surland.de`	DNS	Current	—	—	—	—
`upload.surland.de`	DNS	Current	—	—	—	—
`uploads.surland.de`	DNS	Current	—	—	—	—
`uptime.surland.de`	DNS	Current	—	—	—	—
`url.surland.de`	DNS	Current	—	—	—	—
`us-east.surland.de`	DNS	Current	—	—	—	—
`us-west.surland.de`	DNS	Current	—	—	—	—
`us.surland.de`	DNS	Current	—	—	—	—
`utility.surland.de`	DNS	Current	—	—	—	—
`varnish.surland.de`	DNS	Current	—	—	—	—
`vault.surland.de`	DNS	Current	—	—	—	—
`vendor.surland.de`	DNS	Current	—	—	—	—
`vendors.surland.de`	DNS	Current	—	—	—	—
`video.surland.de`	DNS	Current	—	—	—	—
`videos.surland.de`	DNS	Current	—	—	—	—
`voip.surland.de`	DNS	Current	—	—	—	—
`vpn.surland.de`	DNS	Current	—	—	—	—
`vpn1.surland.de`	DNS	Current	—	—	—	—
`vpn2.surland.de`	DNS	Current	—	—	—	—
`vpn3.surland.de`	DNS	Current	—	—	—	—
`vps.surland.de`	DNS	Current	—	—	—	—
`waf.surland.de`	DNS	Current	—	—	—	—
`wan.surland.de`	DNS	Current	—	—	—	—
`warehouse.surland.de`	DNS	Current	—	—	—	—
`web.surland.de`	DNS	Current	—	—	—	—
`web1.surland.de`	DNS	Current	—	—	—	—
`web2.surland.de`	DNS	Current	—	—	—	—
`webex.surland.de`	DNS	Current	—	—	—	—
`webinar.surland.de`	DNS	Current	—	—	—	—
`webinars.surland.de`	DNS	Current	—	—	—	—
`webmail.surland.de`	DNS	Current	—	—	—	—
`websocket.surland.de`	DNS	Current	—	—	—	—
`whm.surland.de`	DNS	Current	—	—	—	—
`wiki.surland.de`	DNS	Current	—	—	—	—
`wordpress.surland.de`	DNS	Current	—	—	—	—
`work.surland.de`	DNS	Current	—	—	—	—
`worker.surland.de`	DNS	Current	—	—	—	—
`worker1.surland.de`	DNS	Current	—	—	—	—
`worker2.surland.de`	DNS	Current	—	—	—	—
`workspace.surland.de`	DNS	Current	—	—	—	—
`wp.surland.de`	DNS	Current	—	—	—	—
`ws.surland.de`	DNS	Current	—	—	—	—
`www.new.surland.de`	CT Log	Current	—	2	2026-02-13T07:45:26	Let's Encrypt
`www.surland.de`	CT Log	Current	—	4	2026-02-09T10:18:54	Let's Encrypt
`www1.surland.de`	DNS	Current	—	—	—	—
`www2.surland.de`	DNS	Current	—	—	—	—
`www3.surland.de`	DNS	Current	—	—	—	—
`xml.surland.de`	DNS	Current	—	—	—	—
`zabbix.surland.de`	DNS	Current	—	—	—	—
`zoom.surland.de`	DNS	Current	—	—	—	—

Export Recon (CSV)

Δ Changes Detected: DMARC 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

188.68.47.111

AAAA Synchronized 1 / 1 records

2a03:4000:30:3c1d::11:5469

CAA RFC 8659 §4 0 / 0 records

No records

DMARC _dmarc.surland.de RFC 7489 §6.3 Propagating 1 / 1 records

v=DMARC1;p=quarantine;sp=quarantine;pct=100;rua=mailto:post@michels-marc.de;ruf=mailto:post@michels-marc.de;ri=86400;fo=1;

 v=DMARC1;p=quarantine;sp=quarantine;pct=100;rua=mailto:post@michels-marc.de;ruf=mailto:post@michels-marc.de;ri=86400;fo=1;

MX RFC 5321 Synchronized 2 / 2 records

10 mail.surland.de.

50 mx2f71.netcup.net.

NS RFC 1035 Synchronized 3 / 3 records

root-dns.netcup.net.

third-dns.netcup.net.

root-dns.netcup.net.

second-dns.netcup.net.

SOA RFC 1035 Synchronized 1 / 1 records

root-dns.netcup.net. dnsadmin.netcup.net. 2024101826 3600 7200 1209600 3600

TXT RFC 7208 §4 Synchronized 3 / 3 records

apple-domain-verification=X0k8_LYp6P9s4lEqRiP9e62J-f1U11uPoaS9IehL3XY

apple-domain-verification=OqrA5tpbgwT62W17lFNmmgVVst9n0vps1NCRYkHRcqY

v=spf1 mx a include:servers.mcsv.net ~all

apple-domain-verification=X0k8_LYp6P9s4lEqRiP9e62J-f1U11uPoaS9IehL3XY

apple-domain-verification=OqrA5tpbgwT62W17lFNmmgVVst9n0vps1NCRYkHRcqY

v=spf1 mx a include:servers.mcsv.net ~all

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.

e7fb2067fc44d076867f8219bdd9789faabaf7b43bf72a50a8a440d1cb06d669154c62021b9e84463aa49a4dab464abbf0f643c2cabe54adc08f2d3ff26e2fec

Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 10 Mar 2026, 08:58 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-surland.de.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-surland.de.json

Python 3 (cross-platform)

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

sha3sum (coreutils 9+)

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

Compare the output against the .sha3 file or the checksum API at /api/analysis/7035/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 surland.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 surland.de A

Query AAAA records (IPv6) RFC 1035

dig +noall +answer surland.de AAAA

Query MX records (mail servers) RFC 1035

dig +noall +answer surland.de MX

Query NS records (nameservers) RFC 1035

dig +noall +answer surland.de NS

Query TXT records RFC 1035

dig +noall +answer surland.de TXT

Email Authentication

Check SPF record RFC 7208

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

Check DMARC policy RFC 7489

dig +short _dmarc.surland.de TXT

Check DKIM key for selector 'k1' RFC 6376

dig +short k1._domainkey.surland.de TXT

Check DKIM key for selector 'key1' RFC 6376

dig +short key1._domainkey.surland.de TXT

Check DKIM key for selector 'key2' RFC 6376

dig +short key2._domainkey.surland.de TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035

dig +dnssec +noall +answer surland.de DNSKEY

Check DNSSEC DS records RFC 4035

dig +noall +answer surland.de DS

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

dig +dnssec +cd surland.de A @1.1.1.1

Transport Security

Check TLSA record for mail.surland.de RFC 7672

dig +noall +answer _25._tcp.mail.surland.de TLSA

Check TLSA record for mx2f71.netcup.net RFC 7672

dig +noall +answer _25._tcp.mx2f71.netcup.net TLSA

Verify TLS certificate on primary MX (mail.surland.de) RFC 6698

openssl s_client -starttls smtp -connect mail.surland.de:25 -servername mail.surland.de 2>/dev/null | openssl x509 -noout -subject -dates

Check MTA-STS DNS record RFC 8461

dig +short _mta-sts.surland.de TXT

Fetch MTA-STS policy file RFC 8461

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

Check TLS-RPT record RFC 8460

dig +short _smtp._tls.surland.de TXT

Brand & Trust

Check BIMI record BIMI Draft

dig +short default._bimi.surland.de TXT

Check CAA records (certificate authority authorization) RFC 8659

dig +noall +answer surland.de CAA

DNS Records

Check HTTPS/SVCB records RFC 9460

dig +noall +answer surland.de HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344

dig +noall +answer surland.de CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083

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

Transport Security

Test STARTTLS on primary MX (mail.surland.de) RFC 3207

openssl s_client -starttls smtp -connect mail.surland.de:25 -servername mail.surland.de </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962

curl -s 'https://crt.sh/?q=%25.surland.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://surland.de/.well-known/security.txt | head -20

AI Surface

Check for llms.txt

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

Check robots.txt for AI crawler rules

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

Infrastructure Intelligence

ASN lookup for 188.68.47.111 (Team Cymru)

dig +short 111.47.68.188.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 4850 runs

DKIM

Verified 4669 runs

DMARC

Verified 4834 runs

DANE/TLSA

Verified 4653 runs

DNSSEC

Verified 4831 runs

BIMI

Verified 4668 runs

MTA-STS

Verified 4671 runs

TLS-RPT

Verified 4673 runs

CAA

Verified 4665 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 surland.de A

Query AAAA records (IPv6) (RFC 1035)

dig +noall +answer surland.de AAAA

Query MX records (mail servers) (RFC 1035)

dig +noall +answer surland.de MX

Query NS records (nameservers) (RFC 1035)

dig +noall +answer surland.de NS

Query TXT records (RFC 1035)

dig +noall +answer surland.de TXT

Email Authentication

Check SPF record (RFC 7208)

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

Check DMARC policy (RFC 7489)

dig +short _dmarc.surland.de TXT

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

dig +short k1._domainkey.surland.de TXT

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

dig +short key1._domainkey.surland.de TXT

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

dig +short key2._domainkey.surland.de TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035)

dig +dnssec +noall +answer surland.de DNSKEY

Check DNSSEC DS records (RFC 4035)

dig +noall +answer surland.de DS

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

dig +dnssec +cd surland.de A @1.1.1.1

Transport Security

Check TLSA record for mail.surland.de (RFC 7672)

dig +noall +answer _25._tcp.mail.surland.de TLSA

Check TLSA record for mx2f71.netcup.net (RFC 7672)

dig +noall +answer _25._tcp.mx2f71.netcup.net TLSA

Verify TLS certificate on primary MX (mail.surland.de) (RFC 6698)

openssl s_client -starttls smtp -connect mail.surland.de:25 -servername mail.surland.de 2>/dev/null | openssl x509 -noout -subject -dates

Check MTA-STS DNS record (RFC 8461)

dig +short _mta-sts.surland.de TXT

Fetch MTA-STS policy file (RFC 8461)

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

Check TLS-RPT record (RFC 8460)

dig +short _smtp._tls.surland.de TXT

Brand & Trust

Check BIMI record (BIMI Draft)

dig +short default._bimi.surland.de TXT

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

dig +noall +answer surland.de CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460)

dig +noall +answer surland.de HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344)

dig +noall +answer surland.de CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083)

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

Transport Security

Test STARTTLS on primary MX (mail.surland.de) (RFC 3207)

openssl s_client -starttls smtp -connect mail.surland.de:25 -servername mail.surland.de </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962)

curl -s 'https://crt.sh/?q=%25.surland.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://surland.de/.well-known/security.txt | head -20

AI Surface

Check for llms.txt

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

Check robots.txt for AI crawler rules

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

Infrastructure Intelligence

ASN lookup for 188.68.47.111 (Team Cymru)

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

Engineer's DNS Intelligence Report

Email Security Methodology Can this domain be impersonated by email? Unlikely SPF and DMARC quarantine 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? Likely DMARC quarantine flags but does not reject spoofed mail (RFC 7489 §6.3) — no BIMI or CAA (RFC 8659) reinforcement leaves brand impersonation largely unaddressed

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

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

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 (1 item)

Public Exposure Checks Are sensitive files or secrets exposed? No

DNS Server Security Hardened

Delegation Consistency 1 Issue

Nameserver Fleet Matrix 2 Issues

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? 488 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? Unlikely SPF and DMARC quarantine 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? Likely DMARC quarantine flags but does not reject spoofed mail (RFC 7489 §6.3) — no BIMI or CAA (RFC 8659) reinforcement leaves brand impersonation largely unaddressed

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

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

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 (1 item)

Public Exposure Checks Are sensitive files or secrets exposed? No

DNS Server Security Hardened

Delegation Consistency 1 Issue

Nameserver Fleet Matrix 2 Issues

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? 488 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