Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 14 Feb 2026, 18:51 UTC
Duration 10.7s
Version v26.14.17
Integrity da33e8855e87611d3577b6143f9ff019e89d1c7246972784364a3d3727e0531195dd62aa4df3f6c4f08399c4a3786c91e21255a58c7bdeac5595cd38c30aea77
Subject Domain
spitalgiurgiu.ro

Engineer's DNS Intelligence Report

spitalgiurgiu.ro
14 Feb 2026, 18:51 UTC · 10.7s ·v26.14.17 · SHA-3-512: da33✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint
DNS Security & Trust Posture
Risk Level: Medium Risk
3 protocols configured, 6 not configured Why we go beyond letter grades
1 recommendation 1 monitoring
Suggested Scanner Configuration High Confidence
Based on 16 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 39.2s, 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
Partial
Brand Impersonation
Not Setup
DNS Tampering
Unsigned
Certificate Control
Open
Recommended
Enable DMARC aggregate reporting (rua) for authentication visibility
Monitoring
DMARC record has configuration warnings — review recommended
Configured
SPF, DMARC (with warnings), DKIM
Not Configured
MTA-STS, TLS-RPT, BIMI, DANE, DNSSEC, CAA
Registrar (RDAP) LIVE
Unknown
Where domain was purchased
Email Service Provider
Unknown
Where email is hosted (MX)
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? Uncertain incomplete configuration

SPF Record RFC 7208 §4 Verified

Does this domain declare who may send email on its behalf? Yes
Success ~all 1/10 lookups

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

v=spf1 ip4:185.236.84.126 ip4:188.215.250.201 +a +mx +ip4:188.212.156.28 +ip4:89.46.7.183 +ip4:92.114.94.105 ~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.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? No policy published
Warning

No DMARC record found

RFC 7489 Present — DMARC record published per RFC 7489 §6.3.
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

Found DKIM records for 1 selector(s)

default._domainkey
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0jqwyzE2OWzTYX8Ri/W5tqnoyxMFDmBX9ZgrYqKIzGm18fTtXewEgMn/8EMhXdwHA5KKYMgBxgKZG2R6aA7cF3saxpcTRUenrfLgSpEkV2vbfa9Adi1zndZ9Sr7LqV1TE+iVSe2nVtAHTWdz8wXhmJ+QxkXR+o2Js6XE4QjSASGmopilnMl9a9hS0KrQX0+P9ZTC+6YAcZrvuqb1NM57GrJQHU9uA9hoE0k8WXC9AQwJQdxnVqmxADAbAAMKtEbTrqz0tjD4Lf19gqligdn6xdkpoBtyt9iq8UoNf1CnGtmH/og07YGwG1CySxwwG6wEapgvIeWJuutTlD7/2l9XJwIDAQAB;
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

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 1 MX host)

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

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)
TypeDetailSeverityConfidence
robots_txt_no_ai_blocks robots.txt found but no AI-specific blocking directives low Observed
Mail Transport Security Beta Is mail transport encrypted and verified? Not Enforced

Port 25 not reachable from this host

MX Host STARTTLS TLS Version Cipher Certificate
spitalgiurgiu.ro N/A N/A N/A
SMTP port 25 may be blocked by hosting provider — this is common for cloud platforms
Summary: 0/1 reachable, 0 STARTTLS, 0 valid certs
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)

ASNNameCountry
AS44043 RO
IPv4 Mappings:
185.236.84.126 → AS44043 (185.236.84.0/24)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success

No SaaS verification records detected

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.

Domain Security Methodology Can DNS responses be tampered with in transit? Possible

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

2 nameserver(s) configured

Nameservers: ns3.fashionit.ro ns4.fashionit.ro
Multi-Resolver Verification Recon: Consensus reached - 4 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

185.236.84.126
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

0 spitalgiurgiu.ro.
Priority + mail server for email delivery

SRVServices

_caldavs._tcp: 0 0 2080 spitalgiurgiu.ro.
_autodiscover._tcp: 0 0 443 cpanelemaildiscovery.cpanel.net.
_carddavs._tcp: 0 0 2080 spitalgiurgiu.ro.
SIP, XMPP, or other service endpoints
Web: Reachable (1 IPv4, 0 IPv6) Mail: 1 server Services: 3 endpoints
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 23 subdomains discovered
How did we find these?
Certificate Transparency Logs Unavailable The results below are from DNS probing only and may be significantly incomplete. CT logs typically reveal hundreds or thousands of additional subdomains via certificate issuance history (RFC 6962).
Re-Analyze to Retry CT Lookup
94 certificates analyzed current expired Source: Certificate Transparency Logs
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
CT Log Expired — 4 — —
CT Log Expired — 2 — —
CT Log Expired — 64 — —
CT Log Expired — 4 — —
CT Log Expired — 2 — —
CT Log Expired — 46 — —
CT Log Expired — 4 — —
CT Log Expired — 2 — —
CT Log Expired — 46 — —
CT Log Expired — 4 — —
CT Log Expired — 2 — —
CT Log Expired — 64 — —
CT Log Expired — 10 — —
CT Log Expired — 6 — —
CT Log Expired — 4 — —
CT Log Expired — 2 — —
CT Log Expired — 64 — —
CT Log Expired — 4 — —
CT Log Expired — 2 — —
CT Log Expired — 64 — —
CT Log Expired — 7 — —
CT Log Expired — 4 — —
CT Log Expired — 64 — —
Export Recon (CSV)
Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.
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
185.236.84.126
185.236.84.126
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 0 / 0 records
No records
No records
MX RFC 5321 Synchronized 1 / 1 records
0 spitalgiurgiu.ro.
0 spitalgiurgiu.ro.
NS RFC 1035 Synchronized 2 / 2 records
ns4.fashionit.ro.
ns4.fashionit.ro.
ns3.fashionit.ro.
ns3.fashionit.ro.
SOA RFC 1035 Synchronized 1 / 1 records
ns3.fashionit.ro. server.mxserver.ro. 2026020701 3600 1800 1209600 86400
ns3.fashionit.ro. server.mxserver.ro. 2026020701 3600 1800 1209600 86400
TXT RFC 7208 §4 Synchronized 1 / 1 records
v=spf1 ip4:185.236.84.126 ip4:188.215.250.201 +a +mx +ip4:188.212.156.28 +ip4:89.46.7.183 +ip4:92.114.94.105 ~all
v=spf1 ip4:185.236.84.126 ip4:188.215.250.201 +a +mx +ip4:188.212.156.28 +ip4:89.46.7.183 +ip4:92.114.94.105 ~all
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA

When was a record added, removed, or changed — and could that change be the problem?

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.

da33e8855e87611d3577b6143f9ff019e89d1c7246972784364a3d3727e0531195dd62aa4df3f6c4f08399c4a3786c91e21255a58c7bdeac5595cd38c30aea77
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 14 Feb 2026, 18:51 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-spitalgiurgiu.ro.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-spitalgiurgiu.ro.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-spitalgiurgiu.ro.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-spitalgiurgiu.ro.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/869/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 spitalgiurgiu.ro. 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 spitalgiurgiu.ro A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer spitalgiurgiu.ro AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer spitalgiurgiu.ro MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer spitalgiurgiu.ro NS
Query TXT records RFC 1035 
dig +noall +answer spitalgiurgiu.ro TXT

Email Authentication

Check SPF record RFC 7208 
dig +short spitalgiurgiu.ro TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.spitalgiurgiu.ro TXT
Check DKIM key for selector 'default' RFC 6376 
dig +short default._domainkey.spitalgiurgiu.ro TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035 
dig +dnssec +noall +answer spitalgiurgiu.ro DNSKEY
Check DNSSEC DS records RFC 4035 
dig +noall +answer spitalgiurgiu.ro DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035 
dig +dnssec +cd spitalgiurgiu.ro A @1.1.1.1

Transport Security

Check TLSA record for spitalgiurgiu.ro RFC 7672 
dig +noall +answer _25._tcp.spitalgiurgiu.ro TLSA
Verify TLS certificate on primary MX (spitalgiurgiu.ro) RFC 6698 
openssl s_client -starttls smtp -connect spitalgiurgiu.ro:25 -servername spitalgiurgiu.ro 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461 
dig +short _mta-sts.spitalgiurgiu.ro TXT
Fetch MTA-STS policy file RFC 8461 
curl -sL https://mta-sts.spitalgiurgiu.ro/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460 
dig +short _smtp._tls.spitalgiurgiu.ro TXT

Brand & Trust

Check BIMI record BIMI Draft 
dig +short default._bimi.spitalgiurgiu.ro TXT
Check CAA records (certificate authority authorization) RFC 8659 
dig +noall +answer spitalgiurgiu.ro CAA

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer spitalgiurgiu.ro HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer spitalgiurgiu.ro CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/spitalgiurgiu.ro' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (spitalgiurgiu.ro) RFC 3207 
openssl s_client -starttls smtp -connect spitalgiurgiu.ro:25 -servername spitalgiurgiu.ro </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962 
curl -s 'https://crt.sh/?q=%25.spitalgiurgiu.ro&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://spitalgiurgiu.ro/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://spitalgiurgiu.ro/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://spitalgiurgiu.ro/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 185.236.84.126 (Team Cymru) 
dig +short 126.84.236.185.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 spitalgiurgiu.ro A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer spitalgiurgiu.ro AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer spitalgiurgiu.ro MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer spitalgiurgiu.ro NS
Query TXT records (RFC 1035) 
dig +noall +answer spitalgiurgiu.ro TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short spitalgiurgiu.ro TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.spitalgiurgiu.ro TXT
Check DKIM key for selector 'default' (RFC 6376) 
dig +short default._domainkey.spitalgiurgiu.ro TXT

Domain Security

Check DNSSEC DNSKEY records (RFC 4035) 
dig +dnssec +noall +answer spitalgiurgiu.ro DNSKEY
Check DNSSEC DS records (RFC 4035) 
dig +noall +answer spitalgiurgiu.ro DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) (RFC 4035) 
dig +dnssec +cd spitalgiurgiu.ro A @1.1.1.1

Transport Security

Check TLSA record for spitalgiurgiu.ro (RFC 7672) 
dig +noall +answer _25._tcp.spitalgiurgiu.ro TLSA
Verify TLS certificate on primary MX (spitalgiurgiu.ro) (RFC 6698) 
openssl s_client -starttls smtp -connect spitalgiurgiu.ro:25 -servername spitalgiurgiu.ro 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record (RFC 8461) 
dig +short _mta-sts.spitalgiurgiu.ro TXT
Fetch MTA-STS policy file (RFC 8461) 
curl -sL https://mta-sts.spitalgiurgiu.ro/.well-known/mta-sts.txt
Check TLS-RPT record (RFC 8460) 
dig +short _smtp._tls.spitalgiurgiu.ro TXT

Brand & Trust

Check BIMI record (BIMI Draft) 
dig +short default._bimi.spitalgiurgiu.ro TXT
Check CAA records (certificate authority authorization) (RFC 8659) 
dig +noall +answer spitalgiurgiu.ro CAA

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer spitalgiurgiu.ro HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer spitalgiurgiu.ro CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/spitalgiurgiu.ro' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (spitalgiurgiu.ro) (RFC 3207) 
openssl s_client -starttls smtp -connect spitalgiurgiu.ro:25 -servername spitalgiurgiu.ro </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962) 
curl -s 'https://crt.sh/?q=%25.spitalgiurgiu.ro&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://spitalgiurgiu.ro/.well-known/security.txt | head -20

AI Surface

Check for llms.txt 
curl -sI https://spitalgiurgiu.ro/llms.txt | head -5
Check robots.txt for AI crawler rules 
curl -s https://spitalgiurgiu.ro/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 185.236.84.126 (Team Cymru) 
dig +short 126.84.236.185.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

spitalgiurgiu.ro

0s
DNS records — Cloudflare, Google, Quad9, OpenDNS, DNS4EU
Email auth — SPF, DMARC, DKIM selectors
DNSSEC chain of trust & DANE/TLSA
Certificate Transparency & subdomain discovery
SMTP transport & STARTTLS verification
MTA-STS, TLS-RPT, BIMI, CAA
Registrar & infrastructure analysis
Intelligence Classification & Interpretation

Every result includes terminal commands you can run to independently verify the underlying data. No proprietary magic.