Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 21 Feb 2026, 21:24 UTC
Duration 82.2s
Version v26.23.50
Integrity e1f38bd78ff876c16d40cc3fc9af4fdfbc6eddfc056f16945bc4ddc33de4f12913340e646c4bebbdeec9824c80748eee25faeb5b1641a82332aa65f6791a6660
Subject Domain
tesla.com

Engineer's DNS Intelligence Report

tesla.com
21 Feb 2026, 21:24 UTC · 82.2s ·v26.23.50 · SHA-3-512: e1f3✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint Microsoft 365 5 SaaS Services
DNS Security & Trust Posture
Risk Level: Low Risk
3 protocols configured, 5 not configured, 1 unavailable on provider Why we go beyond letter grades
2 monitoring
Suggested Scanner Configuration High Confidence
Based on 20 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 35.7s, 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
Monitoring
External domain ag.dmarcian.com has not authorized tesla.com to send DMARC reports (missing tesla.com._report._dmarc.ag.dmarcian.com TXT record), External domain fr.dmarcian.com has not authorized tesla.com to send DMARC reports (missing tesla.com._report._dmarc.fr.dmarcian.com TXT record)
Configured
SPF (hard fail), DMARC (reject), DKIM
Not Configured
MTA-STS, TLS-RPT, BIMI, DNSSEC, CAA
Unavailable on Provider
DANE
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
Low Add BIMI Record

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

BIMI displays your verified brand logo next to your emails in supporting mail clients.
TypeTXT
Hostdefault._bimi.tesla.com (BIMI default record)
Valuev=BIMI1; l=https://tesla.com/brand/logo.svg
RFC 9495
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.
TypeCAA
Hosttesla.com (root of domain — adjust CA to match your provider)
Value0 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.
TypeTXT
Host_smtp._tls.tesla.com (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@tesla.com
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.
TypeTXT
Host_mta-sts.tesla.com (MTA-STS policy record)
Valuev=STSv1; id=tesla.com
RFC 8461
Registrar (RDAP) OBSERVED LIVE
MarkMonitor Inc.
Where domain was purchased
Email Service Provider INFERRED
Microsoft 365
Strongly Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Unknown
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? No SPF and DMARC reject policy enforced

SPF Record RFC 7208 §4 Verified

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

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

v=spf1 ip4:54.240.84.225/32 ip4:54.240.84.226/31 ip4:54.240.84.228/30 ip4:54.240.84.232/29 ip4:54.240.84.240/29 ip4:54.240.84.248/30 ip4:54.240.84.252/32 ip4:44.239.249.139 ip4:52.24.70.112 ip4:34.223.204.78 ip4:213.244.145.203 ip4:213.244.145.219 ip4:213.244.145.204 ip4:213.244.145.220 ip4:8.47.24.203 ip4:8.47.24.219 ip4:8.47.24.204 ip4:8.47.24.220 ip4:8.45.124.203 ip4:8.45.124.219 ip4:8.45.124.204 ip4:8.45.124.220 ip4:8.21.14.203 ip4:8.21.14.219 ip4:8.21.14.204 ip4:8.21.14.220 ip4:8.21.14.194 ip4:8.21.14.211 ip4:212.49.145.0/24 ip4:91.103.52.0/22 ip4:168.245.123.10 ip4:216.81.144.165 ip4:149.72.247.52 ip4:149.72.134.64 ip4:149.72.152.236 ip4:149.72.163.58 ip4:149.72.172.170 ip4:167.89.90.62 ip4:158.228.129.79 ip4:216.81.144.165 ip4:117.50.14.178 ip4:117.50.35.199 ip4:54.240.42.110 ip4:54.240.42.111 ip4:199.71.239.178 ip4:67.216.183.10 ip4:8.43.178.222 ip4:64.95.144.196 ip4:199.71.239.52 include:u13494342.wl093.sendgrid.net include:spf.protection.outlook.com include:mail.zendesk.com include:_spfsn.teslamotors.com include:_spf.qualtrics.com include:_spf.ultipro.com include:_spf.psm.knowbe4.com include:spf1.sendcloud.org include:spf2.sendcloud.org -all
RFC 7489 §10.1: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)
SPF hard fail (-all): compliance-strong, but can short-circuit DMARC. RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
DMARC is set to reject — enforcement is strong. However, some receivers may still reject messages on SPF hard fail before DKIM alignment is checked. Switching to ~all + p=reject would provide the same enforcement with full DMARC compatibility.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Yes — reject policy
Success p=reject

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; pct=100; rua=mailto:n2ju30bc@ag.dmarcian.com; ruf=mailto:n2ju30bc@fr.dmarcian.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 reporting (ruf) is configured, but most major providers do not send forensic reports. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record. RFC 7489 §7.3 — Forensic Reports
RFC 7489 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.
DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.
Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Verified

Are outbound emails cryptographically signed? Yes — verified
Found

Found DKIM records for 6 selector(s)

mail._domainkey
k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCFnZ42r5s08PJHkas3ak9VywTrCV849uGT9fyye54mzJ0d9+TrZkgh/7gHwmQ6h44K3jpagDkys8RF1WIGJFqwrAsyBjvDwYzYQ6YZRjq4ICNN46Q6uhkBfp0DVjYHMyR1wFft/LdRW4o2kZKcLnO3BYvJN++bu4TDSbnm6GMBkwIDAQAB
mimecast._domainkey Mimecast
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCmVxkZXvb6xAEl/1Yi3fbqQAh9Y7+EYW6wn4pcGGrFMbstJdXlLEEdHD+vzo0tNbq1pk3tNMT7b3dS6nBHq0paT095dEFG99rm5PrcufZgoScRneC1q4DJSnfJtp5rlSb80K1Td5OZ6ixvSed8F0nxL1L7B2j/DQjVyKmoB9RedQIDAQAB
mx._domainkey
k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDW18+uHG2dK5CgGzFnKNkYWQej5h1uXsuvfj1VE5JhddfpgNKQaL9R2GZw1ndimr17hURVjvNYzhWSqVZpEW3js72Hg28VfDrfiJ/y2ZW1QOqfz7bcwNBlm5kj2PSeyr5srD6ipiDUXdC72nZJILiWoYjkbH6Gc1mJOlAFJESo9QIDAQAB
s1._domainkey SendGrid
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt62P8MbQvYrpBeSCT3eluwATuB8EkEfytsoh4bG91IduePxaEad6nUesO0hbkIfDFPncjqd0/WUKLheu9wt418zsk94WMbhUPXThBcKYo+qFCYkKqbFBmKnKPwT8KHlnB4YAugtNMzv5RWefFopu3BVUnk13s7+RolqLAvDuohVTjPJBJ3XD48d9DFVFxfOx/kMx1ZHQkaEzAupA4vhyX9I/LjAKaeEco/HqWyZsWA2iPj1SDZyvS72tkH/1KVBRAe2aaRLKjxI588OkkE3tKqC2u9iA8Gl4O78QzhkKvYas5gOyPbHl09vyH1Az30W8h7bMKi5AiaImjjopNWc9QQIDAQAB
s2._domainkey SendGrid
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDSOEE3TFmVQhaJkiEXt9oGc2AIOSURK3k28KxKTMh2y7Id+nUKS8WOyi6s4BOgxICQ9GX+ZMQykC1Va3Gak9GqR0OAri5VKLS89hbEGv1iDlmJNuLALi2U/rztFsDOsbbTMk4D2WGyMQ6kzSuviA9xngV3i6ilCSwjtNCGvXH4dQIDAQAB
selector1._domainkey Microsoft 365
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDDrdHMOmLStiYdoFToER3wxvLfG5acW0LIlX2gXCvWgl8T4XFHQiTKQVWBnNGpe0xvjtCq19erx6nBvgNC8aGSGz6cbBqlE+nmBlRSgjbWGI1NvtfBLBHK3y2Lt3S6S/y8b21RQunB9MyOAMOQiCsuT5HeIWtMexzXMd1WstdSjQIDAQAB;
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

2 of 2 external reporting domains missing authorization

External Domain Authorization Auth Record
ag.dmarcian.com Unauthorized —
fr.dmarcian.com Unauthorized —
External domain ag.dmarcian.com has not authorized tesla.com to send DMARC reports (missing tesla.com._report._dmarc.ag.dmarcian.com TXT record)
External domain fr.dmarcian.com has not authorized tesla.com to send DMARC reports (missing tesla.com._report._dmarc.fr.dmarcian.com 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 Available

DANE not available — Microsoft 365 does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Microsoft 365

Microsoft 365 does not support DANE for inbound mail. Microsoft uses its own certificate pinning mechanism.

Recommended alternative: MTA-STS

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. Since Microsoft 365 does not support inbound DANE, deploy MTA-STS (RFC 8461) to enforce TLS and protect against downgrade attacks.

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

Brand Security Can this brand be convincingly faked? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3), but no BIMI brand verification and no CAA certificate restriction (RFC 8659) — visual impersonation via lookalike domains and unrestricted certificate issuance remain open vectors

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 significant AI surface findings

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? No directives
No robots.txt found
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
Public Exposure Checks Are sensitive files or secrets exposed? No

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

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.
What type of scan is this?

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

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

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

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

Transport security inferred from 1 signal(s) — no enforcement policy active

Policy Assessment Primary
  • Microsoft 365 enforces TLS 1.2+ with DANE (GA Oct 2024) and valid certificates
Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
Skipped — SMTP port 25 not reachable from this host — outbound port 25 is likely blocked by the hosting provider. Transport security is assessed via DNS policy records, which is the standards-aligned primary method per NIST SP 800-177 Rev. 1.
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

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

ASNNameCountry
AS33905 NL
IPv4 Mappings:
2.18.51.207 → AS33905 (2.18.51.0/24)
23.40.100.207 → AS33905 (23.40.100.0/24)
2.18.52.207 → AS33905 (2.18.52.0/24)
23.7.244.207 → AS33905 (23.7.244.0/24)
2.18.49.207 → AS ()
2.18.54.207 → AS ()
2.18.48.207 → AS ()
2.18.50.207 → AS ()
2.18.55.207 → AS ()
2.18.53.207 → AS ()

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 5 services

5 SaaS services 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.

ServiceVerification Record
Atlassian atlassian-domain-verification=U31RjXDO5NBJROoOVpVEsKJ7daGpXuXPDF8HeqlmvXUKOtTao6...
Apple apple-domain-verification=CHZ8RLPKu4dlRxlaNa_nR9oA2MjZ1n2fiE9s0QlbRO8
Google Workspace google-site-verification=Y7lbse5bSatjXaqSBOWXjsit4mOp9cQzfLDpnQUSZlg
Adobe adobe-idp-site-verification=321c026a-3a8c-4206-a1fa-391a59585c54
Microsoft 365 MS=ms22358213
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

Enterprise DNS Context: DNSSEC is the only standardized, DNS-verifiable mechanism that cryptographically authenticates responses between authoritative servers and resolvers (RFC 4033 §2, RFC 4035). Without it, DNS responses are technically vulnerable to in-transit tampering. Enterprise operators may employ compensating controls (anycast, DDoS mitigation, private peering, TSIG) — however, these do not provide DNS-layer data authentication to third-party resolvers and are not verifiable via DNS alone.
Visibility: DNS-only — network-layer compensating controls cannot be observed or verified through DNS queries. This assessment reflects what is provable from the DNS evidence available.

NS Delegation Verified

7 nameserver(s) configured

Nameservers: a1-12.akam.net a10-67.akam.net a12-64.akam.net a28-65.akam.net a7-66.akam.net a9-67.akam.net edns69.ultradns.com
Enterprise DNS (Multi-Provider Redundancy)
Nameservers span 2 providers (Akamai, UltraDNS (Neustar/Vercara)). Multi-provider DNS provides resilience against single-provider outages — an enterprise best practice for critical domains.
DNS provider(s): Akamai UltraDNS (Neustar/Vercara)
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (1 difference found)
Resolver Differences:
TXT: OpenDNS returned different results: [MS=ms22358213 SFMC-qkAv7SvlQaslp7NEALX8t68s_AZWOQB6ThKQS5l5 T0E0S29854 _f32sd18rpksw3zh1hgbhaulpv016hoh _i88zzpi9e3jr0xglot953efk0ui36y5 _quuerjb9mywulmdygnzgnt9awyzm15c _w19nckjurfa4aldim48vtbrxsq1phnv apple-domain-verification=C9J7eOtEbm7Dqr88 jamf-site-verification=u4x3LuqSfpoLn5nJ0zMd5g logmein-domain-confirmation=9zxwVn2buGWrLtU24J88]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

2.18.51.207
23.40.100.207
2.18.52.207
23.7.244.207
2.18.49.207
2.18.54.207
2.18.48.207
2.18.50.207
2.18.55.207
2.18.53.207
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

10 tesla-com.mail.protection.outlook.com.
Priority + mail server for email delivery
Microsoft 365

SRVServices

_sipfederationtls._tcp: 100 1 5061 sipfed.online.lync.com.
_sip._tls: 100 1 443 sipdir.online.lync.com.
SIP, XMPP, or other service endpoints
Web: Reachable (10 IPv4, 0 IPv6) Mail: 1 server Services: 2 endpoints
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 185 subdomains discovered
How did we find these?
200 unique certificates 185 current 0 expired 25 CNAMEs Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Wildcard certificate detected: *.tesla.com Active 5 certs 1 CA:
No explicit SANs found on wildcard certificates. Subdomains covered by this wildcard won't appear individually in CT logs (RFC 6962).
DNS probing and CNAME chain traversal were used to discover additional subdomains below.
Certificate Authority Diversity (1 CA observed across CT log history)
Certificate Authority Certs First Issued Last Issued Status
200 2025-01-24 2025-08-29 Active
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
accounts.tesla.com DNS Current accounts.tesla.com.edgekey.net 5 2025-05-23 —
ai-api-stg.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
ai-api-uat.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
ai-api.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
akamai-apigateway-einvoicing-stg.tesla.com CT Log Current — 4 2025-03-16T00:00:00Z
akamai-apigateway-vehicleextinfogw-prdsvc-st.tesla.com CT Log Current akamai-apigateway-vehicleextinfogw-prdsvc-st.tesla.com.edgekey.net 4 2025-03-16T00:00:00Z
akamai-apigateway-vehicleextinfogw-stgsvc-st.tesla.com CT Log Current — 4 2025-03-16T00:00:00Z
apac-cppm.tesla.com CT Log Current — 2 2025-02-11T00:00:00Z
apf-api.eng.vn.cloud.tesla.com CT Log Current — 1 2025-05-20T00:00:00Z
apf-api.prd.vn.cloud.tesla.com CT Log Current d2p1ot6coc1j95.cloudfront.net 1 2025-05-15T00:00:00Z
assets.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
atom.tesla.com DNS Current external-eu-pop.edgekey.net 5 2025-05-23 —
auth.eng.euw1.vn.cloud.tesla.com CT Log Current — 9 2025-08-19T00:00:00Z
auth.eng.usw.vn.cloud.tesla.com CT Log Current — 6 2025-08-18T00:00:00Z
auth.tesla.com DNS Current auth.tesla.com.edgekey.net 5 2025-05-23 —
autobidder.powerhub.energy.tesla.com CT Log Current — 1 2025-06-23T00:00:00Z
autodiscover.tesla.com DNS Current autodiscover.outlook.com 5 2025-05-23 —
avatars.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
bettertime-stage.tesla.com CT Log Current — 8 2025-03-07T00:00:00Z
bettertime.tesla.com CT Log Current — 10 2025-03-04T00:00:00Z
bi.tesla.com DNS Current ipa.teslazta.net.srip.net 5 2025-05-23 —
billing.tesla.com DNS Current billing.tesla.com.edgekey.net 5 2025-05-23 —
chat-staging.bottlerocket.tesla.com CT Log Current — 1 2025-08-07T00:00:00Z
citiapiencprodv5.tesla.com CT Log Current — 1 2025-03-18T00:00:00Z
citiapisslprodv5.tesla.com CT Log Current — 1 2025-03-18T00:00:00Z
codeload.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
consul.bottlerocket.tesla.com CT Log Current — 2 2025-07-29T00:00:00Z
courses.tesla.com DNS Current courses.tesla.com.edgekey.net 5 2025-05-23 —
cx-apac-stg.tesla.com CT Log Current — 1 2025-04-28T00:00:00Z
cx-apac.tesla.com CT Log Current — 1 2025-04-28T00:00:00Z
cx-api-apac-stg.tesla.com CT Log Current — 1 2025-04-28T00:00:00Z
cx-api-apac.tesla.com CT Log Current cx-apac.tesla.com.edgekey.net 1 2025-04-28T00:00:00Z
cxadmin-apac-stg.tesla.com CT Log Current — 1 2025-04-28T00:00:00Z
cxadmin-apac.tesla.com CT Log Current — 1 2025-04-28T00:00:00Z
cxadmin-api-apac-stg.tesla.com CT Log Current — 1 2025-04-28T00:00:00Z
cxadmin-api-apac.tesla.com CT Log Current — 1 2025-04-28T00:00:00Z
dev-hermes-qd.tesla.com CT Log Current — 4 2025-03-16T00:00:00Z
developer.tesla.com DNS Current developer.tesla.com.edgekey.net 5 2025-05-23 —
dhc.tesla.com CT Log Current — 1 2025-07-14T00:00:00Z
digitalassets-contents.tesla.com CT Log Current — 1 2025-02-11T20:26:09Z
digitalassets-secure.tesla.com CT Log Current — 1 2025-05-03T23:41:06Z
digitalassets-shop.tesla.com CT Log Current digitalassets-shop.tesla.com.multicdn.cloudinary.com 1 2025-06-17T23:11:17Z
digitalassets.tesla.com CT Log Current — 1 2025-06-17T23:06:03Z
diner-api-stage.tesla.com CT Log Current — 1 2025-06-17T00:00:00Z
diner-api.tesla.com CT Log Current — 1 2025-06-15T00:00:00Z
diner-webapp-stage.tesla.com CT Log Current — 1 2025-06-17T00:00:00Z
diner-webapp.tesla.com CT Log Current — 1 2025-06-17T00:00:00Z
discovery-service.bottlerocket.tesla.com CT Log Current — 2 2025-08-01T00:00:00Z
discovery.bottlerocket.tesla.com CT Log Current — 2 2025-08-02T00:00:00Z
docker.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
docs.bottlerocket.tesla.com CT Log Current — 1 2025-08-25T00:00:00Z
doraemon-svc-apac-stg.tesla.com CT Log Current — 1 2025-02-11T00:00:00Z
doraemon-svc-apac.tesla.com CT Log Current — 1 2025-02-11T00:00:00Z
embed-staging.bottlerocket.tesla.com CT Log Current — 1 2025-07-23T00:00:00Z
employeefeedback.tesla.com CT Log Current — 1 2025-06-16T00:00:00Z
energy-technician.bottlerocket.tesla.com CT Log Current — 1 2025-08-06T00:00:00Z
energy.bottlerocket.tesla.com CT Log Current — 1 2025-08-06T00:00:00Z
energy.tesla.com CT Log Current — 3 2025-04-10T00:00:00Z
engage.tesla.com CT Log Current — 8 2025-03-11T00:00:00Z
events.tesla.com DNS Current — 5 2025-05-23 —
exp-zcp-cloud-eu-itmfg-staging.tesla.com CT Log Current — 2 2025-03-19T00:00:00Z
exp-zcp-cloud-eu-itmfg.tesla.com CT Log Current — 2 2025-03-19T00:00:00Z
exp-zcp-cloud-na-itmfg-staging.tesla.com CT Log Current — 2 2025-03-19T00:00:00Z
exp-zcp-cloud-na-itmfg.tesla.com CT Log Current — 4 2025-03-16T00:00:00Z
extgithub.tesla.com CT Log Current — 1 2025-04-07T00:00:00Z
feedback.tesla.com CT Log Current — 1 2025-06-16T00:00:00Z
fleet-api.eng.na.vn.cloud.tesla.com CT Log Current — 12 2025-03-31T00:00:00Z
forums.tesla.com DNS Current site-6030136.onvanilla.net 5 2025-05-23 —
genai.tesla.com CT Log Current — 1 2025-08-14T00:00:00Z
gist.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
gridlogic.energy.tesla.com CT Log Current — 1 2025-06-23T00:00:00Z
gridlogic.powerhub.energy.tesla.com CT Log Current — 1 2025-06-23T00:00:00Z
image.emails.tesla.com CT Log Current image-emails.tesla.com 1 2025-05-18T00:00:00Z
inference-eu-staging.bottlerocket.tesla.com CT Log Current — 2 2025-08-06T00:00:00Z
inference-eu.bottlerocket.tesla.com CT Log Current — 3 2025-07-15T00:00:00Z
inference-staging.bottlerocket.tesla.com CT Log Current — 2 2025-08-04T00:00:00Z
inference.bottlerocket.tesla.com CT Log Current — 2 2025-07-15T00:00:00Z
ir.bottlerocket.tesla.com CT Log Current — 1 2025-08-06T00:00:00Z
ir.tesla.com DNS Current ir.tesla.com.edgekey.net 5 2025-05-23 —
link.tesla.com DNS Current link.tesla.com.edgekey.net 5 2025-05-23 —
links.tesla.com DNS Current links.tesla.com.edgekey.net 5 2025-05-23 —
live-data.america.fn.tesla.com CT Log Current — 6 2025-03-18T00:00:00Z
live-data.europe.fn.tesla.com CT Log Current — 6 2025-03-18T00:00:00Z
live-data.fn.tesla.com CT Log Current — 6 2025-03-18T00:00:00Z
live-data.prd.america.fn.tesla.com CT Log Current — 6 2025-03-18T00:00:00Z
live-data.prd.eu.fn.tesla.com CT Log Current — 6 2025-03-18T00:00:00Z
live-data.prd.europe.fn.tesla.com CT Log Current — 6 2025-03-18T00:00:00Z
live-data.prd.euw1.fn.tesla.com CT Log Current — 6 2025-03-18T00:00:00Z
live-data.prd.na.fn.tesla.com CT Log Current — 6 2025-03-18T00:00:00Z
live-data.prd.usw2.fn.tesla.com CT Log Current — 6 2025-03-18T00:00:00Z
logcollector-ext.tesla.com CT Log Current — 4 2025-03-16T00:00:00Z
logtransit-ext.tesla.com CT Log Current — 4 2025-03-16T00:00:00Z
marketing.tesla.com DNS Current — 5 2025-05-23 —
maven.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
media-server-api.eng.vn.cloud.tesla.com CT Log Current usw-eng5x-media-npumedia-prd.teslafleet.akadns.net 1 2025-05-05T00:00:00Z
media-server-dev-api.eng.vn.cloud.tesla.com CT Log Current — 1 2025-05-02T00:00:00Z
media-server-qr-dev.eng.america.vn.cloud.tesla.com CT Log Current — 1 2025-05-02T00:00:00Z
media-server-qr.eng.america.vn.cloud.tesla.com CT Log Current — 1 2025-05-05T00:00:00Z
media.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
meet.tesla.com DNS Current group301.tesla.com.akadns.net 5 2025-05-23 —
mobile-links.eng.vn.cloud.tesla.com CT Log Current npuca-eng.usw.vn.cloud.tesla.com 7 2025-04-09T00:00:00Z
mobile.tesla.com DNS Current mobile.tesla.com.edgekey.net 5 2025-05-23 —
monitoring.tesla.com DNS Current — 5 2025-05-23 —
notebooks.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
npm.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
nuget.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
obs.tesla.com CT Log Current — 1 2025-04-17T00:00:00Z
ownerapi-alpha.prd.vn.cloud.tesla.com CT Log Current epuca-eng.usw.vn.cloud.tesla.com 7 2025-04-08T00:00:00Z
ownerapi-api.eng.euw1.vn.cloud.tesla.com CT Log Current — 3 2025-05-01T00:00:00Z
ownerapi-api.eng.usw.vn.cloud.tesla.com CT Log Current — 4 2025-05-01T00:00:00Z
ownerapi-api.eng.usw2.vn.cloud.tesla.com CT Log Current — 3 2025-05-01T00:00:00Z
pages.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
partners.tesla.com DNS Current partners.tesla.com.edgekey.net 5 2025-05-23 —
pay.tesla.com DNS Current static-assets-pay.tesla.com-v1.edgekey.net 5 2025-05-23 —
powerhub.energy.tesla.com CT Log Current — 1 2025-06-23T00:00:00Z
profile.tesla.com DNS Current profile.tesla.com.edgekey.net 5 2025-05-23 —
raw.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
render.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
reply.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
rubygems.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
s3-sidekick-ssl.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
s3.a.iad06.tcs.tesla.com CT Log Current — 1 2025-05-12T00:00:00Z
s3.a.smf12.tcs.tesla.com CT Log Current — 1 2025-05-30T00:00:00Z
s3.a.smf13.tcs.tesla.com CT Log Current — 2 2025-05-12T00:00:00Z
schedule.tesla.com DNS Current schedule.tesla.com.edgekey.net 5 2025-05-23 —
sentry.app.tesla.com CT Log Current — 1 2025-05-24T00:00:00Z
service.tesla.com DNS Current service.tesla.com.edgekey.net 5 2025-05-23 —
serviceapp.tesla.com CT Log Current — 2 2025-05-18T00:00:00Z
share.tesla.com DNS Current group301.tesla.com.akadns.net 5 2025-05-23 —
shop.tesla.com DNS Current shop.tesla.com.edgekey.net 5 2025-05-23 —
signaling-alpha.prd.vn.cloud.tesla.com CT Log Current — 6 2025-04-09T00:00:00Z
signaling-robotics.eng.usw.vn.cloud.tesla.com CT Log Current — 1 2025-06-06T00:00:00Z
signaling-robotics.eng.vn.cloud.tesla.com CT Log Current — 4 2025-04-17T00:00:00Z
sso-dev.tesla.com CT Log Current — 1 2025-01-24T00:00:00Z
sso.tesla.com CT Log Current tslaso.edgekey.net 1 2025-01-24T00:00:00Z
staging.bottlerocket.tesla.com CT Log Current — 2 2025-08-01T00:00:00Z
static.tesla.com DNS Current static.tesla.com.edgekey.net 5 2025-05-23 —
stream.tesla.com DNS Current stream.tesla.com.edgekey.net 5 2025-05-23 —
sts-broker.bottlerocket.tesla.com CT Log Current — 3 2025-07-17T00:00:00Z
taffy.bottlerocket.tesla.com CT Log Current — 1 2025-08-06T00:00:00Z
tesla-inc-docsys-eorg.tesla.com CT Log Current — 1 2025-04-02T00:00:00Z
teslacmgap01.tesla.com CT Log Current — 1 2025-02-12T00:00:00Z
teslacmgcn01.tesla.com CT Log Current — 1 2025-02-12T00:00:00Z
teslacmgeu01.tesla.com CT Log Current — 1 2025-02-12T00:00:00Z
teslacmgna01.tesla.com CT Log Current — 1 2025-08-18T00:00:00Z
teslacmgus01.tesla.com CT Log Current teslacmgus01.westus.cloudapp.azure.com 1 2025-02-12T00:00:00Z
teslamezcal.tesla.com CT Log Current — 1 2025-06-02T00:00:00Z
tf-poc.tesla.com CT Log Current — 1 2025-08-15T00:00:00Z
tokens-staging.bottlerocket.tesla.com CT Log Current — 1 2025-08-07T00:00:00Z
tracking.tesla.com DNS Current external-na-pop1.edgekey.net 5 2025-05-23 —
tripx-alpha.prd.vn.cloud.tesla.com CT Log Current — 11 2025-04-04T00:00:00Z
tripx.eng.usw.vn.cloud.tesla.com CT Log Current — 8 2025-04-11T00:00:00Z
tripx.eng.usw2.vn.cloud.tesla.com CT Log Current — 8 2025-04-14T00:00:00Z
tripx.prd.euw1.vn.cloud.tesla.com CT Log Current — 3 2025-04-16T00:00:00Z
tripx.prd.usw2.vn.cloud.tesla.com CT Log Current — 3 2025-03-19T00:00:00Z
tripx.prd.vn.cloud.tesla.com CT Log Current — 3 2025-06-12T00:00:00Z
triton-management-stg.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
triton-management-uat.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
triton-management.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
triton-server-stg.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
triton-server-uat.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
triton-server.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
tvs-api-stg.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
tvs-api-uat.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
tvs-api.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
tvs-stg.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
tvs-uat.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
tvs.tesla.com CT Log Current — 1 2025-02-04T00:00:00Z
tx.tesla.com CT Log Current — 4 2025-05-13T00:00:00Z
uploads.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
vdi.tesla.com CT Log Current — 1 2025-04-06T00:00:00Z
vehicle-files.eng.euw1.vn.cloud.tesla.com CT Log Current — 1 2025-04-24T00:00:00Z
vehicle-files.eng.usw2.vn.cloud.tesla.com CT Log Current vehicle-files.eng.usw2.vn.cloud.tesla.com.edgekey.net 1 2025-04-24T00:00:00Z
vehicle-files.prd.euw1.vn.cloud.tesla.com CT Log Current — 1 2025-04-24T00:00:00Z
vehicle-files.prd.usw2.vn.cloud.tesla.com CT Log Current vehicle-files.prd.usw2.vn.cloud.tesla.com.edgekey.net 1 2025-04-24T00:00:00Z
veritas-staging.bottlerocket.tesla.com CT Log Current — 3 2025-07-14T00:00:00Z
viewscreen.github.tesla.com CT Log Current — 1 2025-02-07T00:00:00Z
vms.iad06.tcs.tesla.com CT Log Current — 1 2025-05-12T00:00:00Z
vms.smf13.tcs.tesla.com CT Log Current — 1 2025-05-12T00:00:00Z
vpn2.tesla.com DNS Current — 5 2025-05-23 —
warehouse.tesla.com DNS Current warehouse.tesla.com.edgekey.net 5 2025-05-23 —
www.tesla.com CT Log Current — 2 2025-05-18T00:00:00Z
x3-eng.obs.tesla.com CT Log Current — 1 2025-04-17T00:00:00Z
x3-prod.obs.tesla.com CT Log Current x3-prod-geo.tesla.com.akadns.net 1 2025-04-17T00:00:00Z
Export Recon (CSV)
Δ Changes Detected: TXT Resolver ≠ Authoritative (TTL / CDN rotation / recent change)
Risk: Low - typically resolves within TTL
DNS Intelligence What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records (Public DNS cache)
Authoritative Records (Source of truth)
A Synchronized 10 / 10 records
2.18.51.207
23.7.244.207
23.40.100.207
2.18.49.207
2.18.52.207
23.40.100.207
23.7.244.207
2.18.54.207
2.18.49.207
2.18.50.207
2.18.54.207
2.18.55.207
2.18.48.207
2.18.53.207
2.18.50.207
2.18.51.207
2.18.55.207
2.18.48.207
2.18.53.207
2.18.52.207
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 0 / 0 records
No records
No records
DMARC _dmarc.tesla.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject; pct=100; rua=mailto:n2ju30bc@ag.dmarcian.com; ruf=mailto:n2ju30bc@fr.dmarcian.com; fo=1
v=DMARC1; p=reject; pct=100; rua=mailto:n2ju30bc@ag.dmarcian.com; ruf=mailto:n2ju30bc@fr.dmarcian.com; fo=1
MX RFC 5321 Synchronized 1 / 1 records
10 tesla-com.mail.protection.outlook.com.
10 tesla-com.mail.protection.outlook.com.
NS RFC 1035 Synchronized 7 / 7 records
a10-67.akam.net.
a9-67.akam.net.
a12-64.akam.net.
a12-64.akam.net.
a7-66.akam.net.
edns69.ultradns.com.
a28-65.akam.net.
a7-66.akam.net.
edns69.ultradns.com.
a28-65.akam.net.
a9-67.akam.net.
a1-12.akam.net.
a1-12.akam.net.
a10-67.akam.net.
SOA RFC 1035 Synchronized 1 / 1 records
edns69.ultradns.com. domain.teslamotors.com. 2016025183 1800 86400 86400 86400
edns69.ultradns.com. domain.teslamotors.com. 2016025183 1800 86400 86400 86400
TXT RFC 7208 §4 Propagating 31 / 1 records
_f32sd18rpksw3zh1hgbhaulpv016hoh
_f32sd18rpksw3zh1hgbhaulpv016hoh
adobe-sign-verification=efb2da198047b7a154bd604d2721038b
—
atlassian-domain-verification=U31RjXDO5NBJROoOVpVEsKJ7daGpXuXPDF8HeqlmvXUKOtTao652TOMtejHrohKB
—
ms-domain-verification=820e4be7-563e-4f52-b73a-5c9ecdd2fda4
—
apple-domain-verification=CHZ8RLPKu4dlRxlaNa_nR9oA2MjZ1n2fiE9s0QlbRO8
—
cursor-domain-verification-6kgt2s=sxbxrRmk2tNjItWtmh1swmBM0
—
_w19nckjurfa4aldim48vtbrxsq1phnv
—
T0E0S29854
—
jamf-site-verification=u4x3LuqSfpoLn5nJ0zMd5g
—
apple-domain-verification=C9J7eOtEbm7Dqr88
—
55zNJIDU0xk94IfGJtL+Hh+wje5JzOS6GY+ntggZF908AUsx0LBKgr+Nln3CgZEUifxSuN09M05jYpdbd6+cpw==
—
google-site-verification=Y7lbse5bSatjXaqSBOWXjsit4mOp9cQzfLDpnQUSZlg
—
docker-verification=74d1ec4e-a7a6-48a7-9568-9bd0faac833f
—
teamviewer-sso-verification=2fc989f75b19494fab5eb0e2c22dd625
—
ms-domain-verification=e335cec9-0ff5-4a54-b8bc-8966a8d146db
—
dell-technologies-domain-verification=tesla.com_c363f56d-9650-430a-82d3-04ac2257c64a_1756487968
—
domain-verification=0f075f7f33bd0e577c0a56c5bb071f9eedadba45f32da11304913c6afd4b99c7
—
logmein-domain-confirmation=9zxwVn2buGWrLtU24J88
—
adobe-idp-site-verification=321c026a-3a8c-4206-a1fa-391a59585c54
—
google-site-verification=Xg2DEUg2oCz1q9RMx8gh2htHK16_GG9cZXY_eyeSf6w
—
SFMC-qkAv7SvlQaslp7NEALX8t68s_AZWOQB6ThKQS5l5
—
MS=ms22358213
—
_i88zzpi9e3jr0xglot953efk0ui36y5
—
bugcrowd-verification=40bd5dd89a6e4073ca9bc76feac3a47b
—
onetrust-domain-verification=79a1328740f44bc48dd97ab52c0c3377
—
onetrust-domain-verification=480735b10e124e23916192d7e4321902
—
logmein-verification-code=JFAnsPovogeJ4IeW5MXCU3r0C
—
v=spf1 ip4:54.240.84.225/32 ip4:54.240.84.226/31 ip4:54.240.84.228/30 ip4:54.240.84.232/29 ip4:54.240.84.240/29 ip4:54.240.84.248/30 ip4:54.240.84.252/32 ip4:44.239.249.139 ip4:52.24.70.112 ip4:34.223.204.78 ip4:213.244.145.203 ip4:213.244.145.219 ip4:213.244.145.204 ip4:213.244.145.220 ip4:8.47.24.203 ip4:8.47.24.219 ip4:8.47.24.204 ip4:8.47.24.220 ip4:8.45.124.203 ip4:8.45.124.219 ip4:8.45.124.204 ip4:8.45.124.220 ip4:8.21.14.203 ip4:8.21.14.219 ip4:8.21.14.204 ip4:8.21.14.220 ip4:8.21.14.194 ip4:8.21.14.211 ip4:212.49.145.0/24 ip4:91.103.52.0/22 ip4:168.245.123.10 ip4:216.81.144.165 ip4:149.72.247.52 ip4:149.72.134.64 ip4:149.72.152.236 ip4:149.72.163.58 ip4:149.72.172.170 ip4:167.89.90.62 ip4:158.228.129.79 ip4:216.81.144.165 ip4:117.50.14.178 ip4:117.50.35.199 ip4:54.240.42.110 ip4:54.240.42.111 ip4:199.71.239.178 ip4:67.216.183.10 ip4:8.43.178.222 ip4:64.95.144.196 ip4:199.71.239.52 include:u13494342.wl093.sendgrid.net include:spf.protection.outlook.com include:mail.zendesk.com include:_spfsn.teslamotors.com include:_spf.qualtrics.com include:_spf.ultipro.com include:_spf.psm.knowbe4.com include:spf1.sendcloud.org include:spf2.sendcloud.org -all
—
traction-guest=b4f7ad59-bf17-4b3c-8b36-9c2d28f1de32
—
zapier-domain-verification-challenge=64e810e8-0fe1-4de0-b104-229592811c5b
—
_quuerjb9mywulmdygnzgnt9awyzm15c
—
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.

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

Email Authentication

Check SPF record RFC 7208 
dig +short tesla.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.tesla.com TXT
Check DKIM key for selector 'mail' RFC 6376 
dig +short mail._domainkey.tesla.com TXT
Check DKIM key for selector 'mimecast' RFC 6376 
dig +short mimecast._domainkey.tesla.com TXT
Check DKIM key for selector 'mx' RFC 6376 
dig +short mx._domainkey.tesla.com TXT
Check DKIM key for selector 's1' RFC 6376 
dig +short s1._domainkey.tesla.com TXT
Check DKIM key for selector 's2' RFC 6376 
dig +short s2._domainkey.tesla.com TXT
Check DKIM key for selector 'selector1' RFC 6376 
dig +short selector1._domainkey.tesla.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer tesla.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer tesla.com CDS

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 2.18.51.207 (Team Cymru) 
dig +short 207.51.18.2.origin.asn.cymru.com TXT
ASN lookup for 23.40.100.207 (Team Cymru) 
dig +short 207.100.40.23.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 4858 runs
DKIM
Verified 4677 runs
DMARC
Verified 4842 runs
DANE/TLSA
Verified 4661 runs
DNSSEC
Verified 4839 runs
BIMI
Verified 4676 runs
MTA-STS
Verified 4679 runs
TLS-RPT
Verified 4681 runs
CAA
Verified 4673 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 tesla.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer tesla.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer tesla.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer tesla.com NS
Query TXT records (RFC 1035) 
dig +noall +answer tesla.com TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short tesla.com TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.tesla.com TXT
Check DKIM key for selector 'mail' (RFC 6376) 
dig +short mail._domainkey.tesla.com TXT
Check DKIM key for selector 'mimecast' (RFC 6376) 
dig +short mimecast._domainkey.tesla.com TXT
Check DKIM key for selector 'mx' (RFC 6376) 
dig +short mx._domainkey.tesla.com TXT
Check DKIM key for selector 's1' (RFC 6376) 
dig +short s1._domainkey.tesla.com TXT
Check DKIM key for selector 's2' (RFC 6376) 
dig +short s2._domainkey.tesla.com TXT
Check DKIM key for selector 'selector1' (RFC 6376) 
dig +short selector1._domainkey.tesla.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer tesla.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer tesla.com CDS

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 2.18.51.207 (Team Cymru) 
dig +short 207.51.18.2.origin.asn.cymru.com TXT
ASN lookup for 23.40.100.207 (Team Cymru) 
dig +short 207.100.40.23.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

tesla.com

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.