Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 9 Mar 2026, 14:25 UTC
Duration 25.3s
Version v26.35.32
Integrity 7257d8486fc3c36f6d96407656e2de5d4705ffcc2206c34108f8989479b258a4553c6750d2102e8ac085510f13b34b0e4444f1844807b85fb7ab9740a41f9397
Subject Domain
apple.com

Engineer's DNS Intelligence Report

apple.com
9 Mar 2026, 14:25 UTC · 25.3s ·v26.35.32 · SHA-3-512: 7257✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint 8 SaaS Services
DNS Security & Trust Posture
Risk Level: Low Risk
5 protocols configured, 4 not configured Domain appears to be in deliberate DMARC deployment phase — quarantine fully enforced with reporting, consider upgrading to reject Why we go beyond letter grades
1 recommendation
Analysis Confidence (ICD 203)
MODERATE 66/100
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 61% Currency 72/100 Maturity verified
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Intelligence Currency
Data Currency: Adequate 72/100
ICuAE Details
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Stale
DNS data shows some aging or gaps — consider re-scanning for critical decisions

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

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

Big Picture Questions

  • How often do you actually change this record? If it hasn’t changed in months, a short TTL is generating unnecessary DNS queries without any benefit.
  • Are you preparing for a migration or IP change? Short TTLs make sense temporarily — but should be raised back to 1 hour (3600s) once the change is complete.
  • Every DNS lookup adds 20–150ms of latency. With a 60s TTL, returning visitors trigger a fresh lookup every minute. With 3600s, they get cached responses for an hour — faster page loads, no extra infrastructure needed.
  • Google runs A records at ~30s because they operate a global anycast network and need to steer traffic dynamically. For a typical website without that infrastructure, copying those TTLs increases query volume with zero upside.
Tune TTL for apple.com
Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) Note: Some DNS providers (e.g., AWS Route 53 alias records, Cloudflare proxied records) enforce fixed TTLs that cannot be modified. If a finding targets a record you cannot edit, it reflects the observed value rather than a configuration error on your part.
Primary NS ns-ext-prod.jackfruit.apple.com
Serial 2026030901
Admin dnscontact.apple.com
Provider Unknown
Timer Value RFC 1912 Range
Refresh300s1,200–43,200s (20 min – 12 hrs)
Retry300sFraction of Refresh
Expire3628800s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)300s300–86,400s (5 min – 1 day)
Refresh: SOA Refresh is 5 minutes (300s), below the RFC 1912 recommended minimum of 1,200 seconds.
RFC 1912 §2.2
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 34.4s, 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
Protected
DNS Tampering
Unsigned
Certificate Control
Configured
Recommended
Upgrade DMARC policy from quarantine to reject (p=reject) for maximum spoofing protection
Configured
SPF, DMARC (quarantine, 100%), DKIM, BIMI, CAA
Not Configured
MTA-STS, TLS-RPT, DANE, DNSSEC
Priority Actions 4 total Achievable posture: Secure
Medium Enable DNSSEC

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

RFC 4035
Medium Upgrade DMARC to Reject

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

A reject policy provides the strongest protection against domain spoofing.
TypeTXT
Host_dmarc.apple.com (update existing DMARC record)
Valuev=DMARC1; p=reject; rua=mailto:dmarc-reports@apple.com
RFC 7489 §6.3
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.apple.com (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@apple.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.apple.com (MTA-STS policy record)
Valuev=STSv1; id=apple.com
RFC 8461
Registrar (RDAP) OBSERVED LIVE
Nom-iq Ltd. dba COM LAUDE
Where domain was purchased
Email Service Provider
Unknown
Moderately Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Unknown
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? Unlikely SPF and DMARC quarantine policy enforced

SPF Record RFC 7208 §4 Verified

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

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

v=spf1 include:_spf.apple.com include:_spf-txn.apple.com ~all
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)
~all is the industry standard. Google, Apple, and most providers default to soft fail. CISA (BOD 18-01) and RFC 7489 confirm that DMARC policy — not SPF alone — is the primary enforcement control. Using ~all allows DKIM to be evaluated before a DMARC decision is made. This domain uses ~all + DMARC quarantine — good protection. Moving to p=reject would achieve the strongest stance.

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Quarantined, not rejected
Success p=quarantine

DMARC policy quarantine (100%) - good protection

v=DMARC1; p=quarantine; sp=reject; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;
Alignment: SPF relaxed DKIM relaxed sp=reject
Forensic reporting (ruf) is configured, but most major providers do not send forensic reports. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record. RFC 7489 §7.3 — Forensic Reports
Advanced cryptographic posture detected. Domain appears to be in deliberate DMARC deployment phase — quarantine fully enforced with reporting, consider upgrading to reject
RFC 7489 Present — DMARC record published per RFC 7489 §6.3.
Monitoring Posture Note: Quarantine sequesters authentication failures while preserving full DMARC forensic telemetry (RFC 7489 §7). Some organizations maintain quarantine rather than reject as a deliberate monitoring strategy — failed messages are processed and reported but sequestered from the inbox. See NIST SP 800-177 Rev. 1 for enforcement tradeoffs.
DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.
Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Verified

Are outbound emails cryptographically signed? Yes — verified
Found 2048-bit

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

selector1._domainkey 2048-bit Adequate
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDGh555cVTGrCFyGsKqZyAehAhyNLVzwSCNdtgBSol5e/KboxA6edyqdfl1EL279hNdHM9UWcXcgk/HhKPQdmgzMTA927ZXxrsHxMHjVl7Bid78qOIebr75prj3jxuH8KrZfNe14l/dh6TJZt/SkEncmhbVx/tNy9lrHkN5T7LXjQIDAQAB; n=1024,1483209771,1498848171
selector2._domainkey 2048-bit Adequate
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCw9ZicGGW3gn0iKQfcnOsMVy+uLl+YMFonHmEslnpniYxIZ8z0Fn5nY2Gx/m69EHq05WQ8zQ0hRP8d/B0lrPIm6O3c2hiO1sQrJUnwH3jo0/asN6kRFXjTiU/PdlmWhyLdYSv80zNlKpq7qWnsvtlTfJhatEJATM1gZOtspjqLzQIDAQAB; n=1024,1483209771,1
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 valid 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
rua.agari.com Authorized v=DMARC1;
ruf.agari.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 6 MX hosts)

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

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

  • DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
  • MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).
This domain has neither DANE nor MTA-STS. Mail transport relies on opportunistic TLS without policy enforcement, leaving it vulnerable to downgrade attacks. Deploy DANE (RFC 7672) with DNSSEC for the strongest protection, or MTA-STS (RFC 8461) if DNSSEC is not feasible.

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

Brand Security Can this brand be convincingly faked? Unlikely DMARC quarantine enforced (RFC 7489 §6.3) with BIMI brand verification (VMC-validated logo in inboxes) and CAA certificate restriction (RFC 8659 §4) — all three brand-faking vectors addressed; upgrade to p=reject to block spoofed mail outright instead of flagging

BIMI BIMI Spec Verified Success VMC SVG

Is the brand identity verified and displayed in inboxes? Yes

BIMI with VMC certificate (from Verified CA)

VMC certificate accessible (from Verified CA) - logo displays in Gmail, Apple Mail, and all major providers.
v=BIMI1;l=https://www.apple.com/bimi/v2/apple.svg;a=https://www.apple.com/bimi/v2/apple.pem;
BIMI Logo
Logo validated (SVG) View full logo

CAA RFC 8659 §4 Verified Success IODEF

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only pki.apple.com can issue certificates (wildcard issuance: pki.apple.com per RFC 8659 §4.3)

Authorized CAs: pki.apple.com
0 issuewild "pki.apple.com"
0 issue "pki.apple.com"
0 iodef "mailto:contact_pki@apple.com"
Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? Yes RFC 9116

security.txt properly configured

Contact

https://security.apple.com

Expires

2027-03-04 Valid

Policy

https://security.apple.com/bounty/guidelines/
Acknowledgments
Source: https://apple.com/.well-known/security.txt
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
Public Exposure Checks Are sensitive files or secrets exposed? No

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

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

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

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

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

DNS Server Security Hardened

No DNS server misconfigurations found on b.ns.apple.com — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.

Check Result Detail
Zone Transfer (AXFR) Denied Test inconclusive
Open Recursion Disabled Test inconclusive
Nameserver Identity Hidden Test inconclusive
Cache Snooping Protected Test inconclusive

Tested nameservers: b.ns.apple.com, a.ns.apple.com, c.ns.apple.com, d.ns.apple.com

Delegation Consistency 5 Issues

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

Findings:
  • In-bailiwick NS a.ns.apple.com has no glue records at parent — resolution may fail
  • In-bailiwick NS b.ns.apple.com has no glue records at parent — resolution may fail
  • In-bailiwick NS c.ns.apple.com has no glue records at parent — resolution may fail
  • In-bailiwick NS d.ns.apple.com has no glue records at parent — resolution may fail
  • Could not retrieve NS TTL from parent zone

DS ↔ DNSKEY Alignment Aligned

Glue Record Completeness Incomplete

NameserverIn-BailiwickIPv4 GlueIPv6 GlueStatus
a.ns.apple.com Missing
b.ns.apple.com Missing
c.ns.apple.com Missing
d.ns.apple.com Missing

NS TTL Comparison Drift

Child TTL: 43200s Drift: 0s

SOA Serial Consistency Consistent

a.ns.apple.com: 2.026030901e+09
b.ns.apple.com: 2.026030901e+09
c.ns.apple.com: 2.026030901e+09
d.ns.apple.com: 2.026030901e+09
Nameserver Fleet Matrix Healthy

Analyzed 4 nameserver(s) for apple.com — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial
d.ns.apple.com 204.26.57.1 2620:171:801:714::1 AS42 2026030901
a.ns.apple.com 17.253.200.1 2620:149:ae0::53 AS714 2026030901
b.ns.apple.com 17.253.207.1 2620:149:ae7::53 AS714 2026030901
c.ns.apple.com 204.19.119.1 2620:171:800:714::1 AS42 2026030901
Unique ASNs
2
Unique Operators
0
Unique /24 Prefixes
4
Diversity Score
Good

2 ASNs, 4 /24 prefixes across 4 nameservers

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

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

Policy Assessment Primary

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

Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
Skipped — Remote probe failed (connection failed — probe may be offline) and local port 25 is blocked. Transport security is assessed via DNS policy records per NIST SP 800-177 Rev. 1.
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

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

ASNNameCountry
AS714 US
IPv4 Mappings:
17.253.144.10 → AS714 (17.253.144.0/24)
IPv6 Mappings:
2620:149:af0::10 → AS714 (2620:149:af0::/48)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success 8 services

8 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
Facebook / Meta facebook-domain-verification=n6cqjfucq6plswmtfbwnbbeu1qiq3v
Google Workspace google-site-verification=L5kkMdiFI8npvb6KlHui84fJaCw5G64DWhaDRIAT4_c
Cisco Umbrella cisco-ci-domain-verification=6f3bfb849796a518061f8e8c4356f687a138502d86db7427916...
Atlassian atlassian-domain-verification=mLabq99iaT8kquJechF6l31FAYoNUe3WB7tLpLFUiUYVJCse9S...
Adobe adobe-idp-site-verification=6bd5e74c-a3a0-4781-b2e1-e95399b5e11c
Apple apple-domain-verification=X5Jt76bn3Dnmgzjj
Webex webexdomainverification.8C462=b728ec3f-dfc9-42f9-92cb-9ba8853cbee8
Miro miro-verification=2494d255c4c50b1e521650a0659cbf3fa08b0072
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

4 nameserver(s) configured

Nameservers: a.ns.apple.com b.ns.apple.com c.ns.apple.com d.ns.apple.com
Enterprise DNS (Dedicated Infrastructure)
All 4 nameservers are apple.com-branded, indicating organization-operated DNS infrastructure. This is typical of large enterprises, government agencies, and organizations that maintain full control of their DNS resolution chain.
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (1 difference found)
Resolver Differences:
TXT: OpenDNS returned different results: [77a4a6de-da14-449c-83c4-85366e0f55f9 ValidationTokenValue=77a4a6de-da14-449c-83c4-85366e0f55f9 apple-domain-verification=X5Jt76bn3Dnmgzjj cerner-client-id=22dd1d8a-5e8b-4e1e-80ef-39bcdfd42798 cerner-client-id=ce3abf18-ee87-43b9-9927-9eb24b4bac4a facebook-domain-verification=n6cqjfucq6plswmtfbwnbbeu1qiq3v miro-verification=2494d255c4c50b1e521650a0659cbf3fa08b0072]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

17.253.144.10
Where the domain points for web traffic

AAAAIPv6 Address

2620:149:af0::10
IPv6 ready

MXMail Servers

20 mx-in-sg.apple.com.
20 mx-in-ma.apple.com.
20 mx-in-vib.apple.com.
20 mx-in-hfd.apple.com.
10 mx-in.g.apple.com.
20 mx-in-rn.apple.com.
Priority + mail server for email delivery

SRVServices

_sip._tls: 5 5 5060 gslb-b2b-ext.v.aaplimg.com.
SIP, XMPP, or other service endpoints
Web: Reachable (1 IPv4, 1 IPv6) Mail: 6 servers Services: 1 endpoint
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? None found
How did we find these?

No subdomains found via Certificate Transparency logs, DNS probing, or CNAME chain traversal for this domain. No TLS certificates have been issued and no common service names resolve for subdomains of apple.com.

Δ 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
17.253.144.10
17.253.144.10
AAAA Synchronized 1 / 1 records
2620:149:af0::10
2620:149:af0::10
CAA RFC 8659 §4 Synchronized 3 / 3 records
0 iodef "mailto:contact_pki@apple.com"
0 iodef "mailto:contact_pki@apple.com"
0 issuewild "pki.apple.com"
0 issue "pki.apple.com"
0 issue "pki.apple.com"
0 issuewild "pki.apple.com"
DMARC _dmarc.apple.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=quarantine; sp=reject; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;
v=DMARC1; p=quarantine; sp=reject; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;
MX RFC 5321 Synchronized 6 / 6 records
20 mx-in-sg.apple.com.
10 mx-in.g.apple.com.
20 mx-in-ma.apple.com.
20 mx-in-ma.apple.com.
20 mx-in-vib.apple.com.
20 mx-in-rn.apple.com.
20 mx-in-hfd.apple.com.
20 mx-in-sg.apple.com.
10 mx-in.g.apple.com.
20 mx-in-hfd.apple.com.
20 mx-in-rn.apple.com.
20 mx-in-vib.apple.com.
NS RFC 1035 Synchronized 4 / 4 records
b.ns.apple.com.
a.ns.apple.com.
a.ns.apple.com.
b.ns.apple.com.
c.ns.apple.com.
c.ns.apple.com.
d.ns.apple.com.
d.ns.apple.com.
SOA RFC 1035 Synchronized 1 / 1 records
ns-ext-prod.jackfruit.apple.com. dnscontact.apple.com. 2026030901 300 300 3628800 300
ns-ext-prod.jackfruit.apple.com. dnscontact.apple.com. 2026030901 300 300 3628800 300
TXT RFC 7208 §4 19 / 0 records
facebook-domain-verification=n6cqjfucq6plswmtfbwnbbeu1qiq3v
—
77a4a6de-da14-449c-83c4-85366e0f55f9
—
cerner-client-id=ce3abf18-ee87-43b9-9927-9eb24b4bac4a
—
google-site-verification=L5kkMdiFI8npvb6KlHui84fJaCw5G64DWhaDRIAT4_c
—
cisco-ci-domain-verification=6f3bfb849796a518061f8e8c4356f687a138502d86db742791685059176547dd
—
json:eyJ3aHkiOiJUaGlzIGlzIHRvIHRydW5jYXRlIFVEUCByZXNwb25zZXMgZm9yIFRYVCBxdWVyaWVzIHRvIGFwcGxlLmNvbSIsInBhZGRpbmciOiJpZW4wYWVHaGF0aG9oNmhhaHZpZWphaTNlYXkwYWh2YWhjaGFocXVhZWxlZTBZdWw0cGhpZXRoMHNvNXZpZXllZWNvaDRpZThzaGVlcGllVDNwYWVjaGVpVjZqb2h3aWVwaG82In0K
—
v=spf1 include:_spf.apple.com include:_spf-txn.apple.com ~all
—
google-site-verification=zBSq1mG5ssu2If-C17UAz_MzSZDcx03MVxmeDwMNc5w
—
Dynatrace-site-verification=7d881a7c-c13f-4146-9d27-2731459e2509__iqls0105tagglcsaul0m16ibrf
—
atlassian-domain-verification=mLabq99iaT8kquJechF6l31FAYoNUe3WB7tLpLFUiUYVJCse9SKq83hOJzFkwqrh
—
adobe-idp-site-verification=6bd5e74c-a3a0-4781-b2e1-e95399b5e11c
—
yahoo-verification-key=Ay+djyw0qWQgXKWGA/jstjYryTMrKb+PBXI5l8u5/jw=
—
apple-domain-verification=X5Jt76bn3Dnmgzjj
—
webexdomainverification.8C462=b728ec3f-dfc9-42f9-92cb-9ba8853cbee8
—
cerner-client-id=22dd1d8a-5e8b-4e1e-80ef-39bcdfd42798
—
json:eyJ3aHkiOiJUaGlzIGlzIHRvIHRydW5jYXRlIFVEUCByZXNwb25zZXMgZm9yIFRYVCBxdWVyaWVzIHRvIGFwcGxlLmNvbSIsInBhZGRpbmciOiJxdWFoMGVpamFhNGVlajh0aWVkYWlnaG9jZWljaGFlOGVUb3ppZTVmdTVhaFRoMldlaU00aWsyaHVxdThpZXBoaWVxdW9oc2hlaXBhZWdoOUthZWw3b2NoaWVuZ2llem9lc2g1In0K
—
ValidationTokenValue=77a4a6de-da14-449c-83c4-85366e0f55f9
—
google-site-verification=8M6XjQCzydT62jk8HY3VXPAG-nKDllTRV-JpA3-Ktyw
—
miro-verification=2494d255c4c50b1e521650a0659cbf3fa08b0072
—
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.

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

Email Authentication

Check SPF record RFC 7208 
dig +short apple.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.apple.com TXT
Check DKIM key for selector 'selector1' RFC 6376 
dig +short selector1._domainkey.apple.com TXT
Check DKIM key for selector 'selector2' RFC 6376 
dig +short selector2._domainkey.apple.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

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

Email Authentication

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

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

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

apple.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.