Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 13 Feb 2026, 23:29 UTC
Duration 13.7s
Version v26.12.28
Integrity f39121e786c56ab6acb4fb5f8f452ee5a8ae781d8b21cd2576ed42fe46aefe0042a17cf9842f43530e4d66c7329f7e9e47c53d81e14f9f07935a54d4ee23d107
Subject Domain
innbn-bucuresti.ro

Engineer's DNS Intelligence Report

innbn-bucuresti.ro
13 Feb 2026, 23:29 UTC · 13.7s ·v26.12.28 · SHA-3-512: f391✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint
DNS Security & Trust Posture
Risk Level: Low Risk
3 protocols configured, 4 not configured Why we go beyond letter grades
Email Spoofing
Protected
Brand Impersonation
Not Setup
DNS Tampering
Unsigned
Certificate Control
Open
Configured
SPF (~all), DMARC (reject), DKIM
Not Configured
MTA-STS, TLS-RPT, CAA, DNSSEC
Priority Actions 5 total Achievable posture: Low Risk
Medium Deploy MTA-STS policy

Publish an MTA-STS DNS record and host a policy file at https://mta-sts.innbn-bucuresti.ro/.well-known/mta-sts.txt. This tells senders to require TLS when delivering mail to your domain.

_mta-sts.innbn-bucuresti.ro TXT "v=STSv1; id=20240101"
RFC 8461 §3
Low Add CAA records

Publish CAA DNS records to restrict which Certificate Authorities can issue TLS certificates for your domain. Specify your preferred CA (e.g., letsencrypt.org, digicert.com). CAA is advisory — CAs must check it before issuing, but absence means any CA can issue.

innbn-bucuresti.ro CAA 0 issue "letsencrypt.org"
RFC 8659 §4
Low Configure TLS-RPT reporting

TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain. Helps diagnose MTA-STS and STARTTLS issues.

_smtp._tls.innbn-bucuresti.ro TXT "v=TLSRPTv1; rua=mailto:tls-reports@innbn-bucuresti.ro"
RFC 8460 §3
Low Enable DNSSEC

DNSSEC (DNS Security Extensions) cryptographically signs DNS responses, preventing attackers from forging DNS answers. Contact your DNS hosting provider to enable DNSSEC signing.

RFC 4033 §2
Low Configure BIMI brand logo

Publish a BIMI DNS record pointing to your brand logo (SVG Tiny PS format). For full support in Gmail, you will also need a Verified Mark Certificate (VMC).

default._bimi.innbn-bucuresti.ro TXT "v=BIMI1; l=https://innbn-bucuresti.ro/logo.svg"
BIMI Spec
Registrar (RDAP) LIVE
Unknown
Where domain was purchased
Email Service Provider OBSERVED
Unknown
Email: Enforced
Web Hosting
Unknown
Where website is hosted
DNS Hosting OBSERVED
Unknown
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? No
Verdict: DMARC policy is reject — spoofed messages will be blocked by receiving servers. DKIM keys verified with strong cryptography.

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:94.177.36.66 +a +mx +ip4:89.37.120.230 +ip4:89.44.234.254 +ip4:89.33.124.17 ~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 reject: the strongest compatible security stance, aligned with CISA and RFC guidance.

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; rua=mailto:f8d7b1ce@mxtoolbox.dmarc-report.com; ruf=mailto:f8d7b1ce@forensics.dmarc-report.com; fo=1
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
Forensic reports (ruf) configured - many providers ignore these
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? Yes — verified
Found

Found DKIM records for 1 selector(s)

default._domainkey
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAz+7Lfm2aHzrV0UTW21BmIUCHbYm9O7iDI3uE8hDTlaSrmA/mtv9z9Z2Ipz0+pY4/kzaqt0ahaCRMET4Nuk+naWlLWSa6ROgM3Psx1e50TTqpghHryGNtFe6NhbJhrjH15A2A1qJNvhaWIyRR1xc/gevpRb1PoHNNy3TmcLAE+mC3IjeB88UPUqOXKl1s2OwAT47LT2nNKTCtgcPA+2CRsOWlKiFRrpAZKAA6ZLcCBW5+bB47PgANQBSn604NjQqz0Ox9KR+Gkv+SQI2SLi+fHnxttSDQYmIYHbBC1zfby0VLOcWTbvFJf6QiUStLhTN2a4Rx1JcI45xhdrtyzHt5ZQIDAQAB;
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? Yes — all authorized
Success

All 2 external reporting domains properly authorized

External Domain Authorization Auth Record
mxtoolbox.dmarc-report.com Authorized v=DMARC1
forensics.dmarc-report.com Authorized v=DMARC1
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?
Verdict: No brand protection configured. Any CA can issue certificates and no brand logo verification in place.

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

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
innbn-bucuresti.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
AS39737 RO
IPv4 Mappings:
94.177.36.66 → AS39737 (94.177.32.0/21)

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?

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.primetelecom.ro ns4.primetelecom.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

94.177.36.66
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

0 innbn-bucuresti.ro.
Priority + mail server for email delivery

SRVServices

_autodiscover._tcp: 0 0 443 cpanelemaildiscovery.cpanel.net.
_carddavs._tcp: 0 0 2080 innbn-bucuresti.ro.
_caldavs._tcp: 0 0 2080 innbn-bucuresti.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? Unavailable
How did we find these?

Passive discovery using Certificate Transparency Logs — publicly auditable records of every TLS certificate ever issued. CT log returned HTTP 404

Δ 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
94.177.36.66
94.177.36.66
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 0 / 0 records
No records
No records
DMARC _dmarc.innbn-bucuresti.ro RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject; rua=mailto:f8d7b1ce@mxtoolbox.dmarc-report.com; ruf=mailto:f8d7b1ce@forensics.dmarc-report.com; fo=1
v=DMARC1; p=reject; rua=mailto:f8d7b1ce@mxtoolbox.dmarc-report.com; ruf=mailto:f8d7b1ce@forensics.dmarc-report.com; fo=1
MX RFC 5321 Synchronized 1 / 1 records
0 innbn-bucuresti.ro.
0 innbn-bucuresti.ro.
NS RFC 1035 Synchronized 2 / 2 records
ns4.primetelecom.ro.
ns3.primetelecom.ro.
ns3.primetelecom.ro.
ns4.primetelecom.ro.
SOA RFC 1035 Synchronized 1 / 1 records
ns3.primetelecom.ro. webmaster.primetelecom.ro. 2026010801 3600 1800 1209600 86400
ns3.primetelecom.ro. webmaster.primetelecom.ro. 2026010801 3600 1800 1209600 86400
TXT RFC 7208 §4 Synchronized 1 / 1 records
v=spf1 ip4:94.177.36.66 +a +mx +ip4:89.37.120.230 +ip4:89.44.234.254 +ip4:89.33.124.17 ~all
v=spf1 ip4:94.177.36.66 +a +mx +ip4:89.37.120.230 +ip4:89.44.234.254 +ip4:89.33.124.17 ~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), SecurityTrails (DNS history), 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.

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

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer innbn-bucuresti.ro HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer innbn-bucuresti.ro CDS

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 94.177.36.66 (Team Cymru) 
dig +short 66.36.177.94.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 4886 runs
DKIM
Verified 4704 runs
DMARC
Verified 4869 runs
DANE/TLSA
Verified 4688 runs
DNSSEC
Verified 4867 runs
BIMI
Verified 4703 runs
MTA-STS
Verified 4706 runs
TLS-RPT
Verified 4708 runs
CAA
Verified 4700 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 innbn-bucuresti.ro A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer innbn-bucuresti.ro AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer innbn-bucuresti.ro MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer innbn-bucuresti.ro NS
Query TXT records (RFC 1035) 
dig +noall +answer innbn-bucuresti.ro TXT

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer innbn-bucuresti.ro HTTPS

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

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

innbn-bucuresti.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.