Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 22 Apr 2026, 14:06 UTC
Duration 60.4s
Version v26.47.02
Integrity 1d886c366013c293edc42a9ad2a101cfa685ed9babfca89e3759a77191f94be740beaf5e5d46b4bff402de8e2e32718dd5dac53cd379fdc10de5466a290a0419
Subject Domain
ui.com

Engineer's DNS Intelligence Report

ui.com
22 Apr 2026, 14:06 UTC · 60.4s ·v26.47.02 · SHA-3-512: 1d88✱✱✱✱ Verify ·Cross-Referenced
Executive Topology
Recon Mode Snapshot Re-analyze New Domain
Footprint Google Workspace 8 SaaS Services
DNS Security & Trust Posture
Risk Level: Low Risk
4 protocols configured, 4 not configured, 1 unavailable on provider Why we go beyond letter grades
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 64% Currency 69/100 Maturity consistent
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Stale
ICuAE Details
DNS data shows some aging or gaps — consider re-scanning for critical decisions
Enterprise Traffic Engineering Detected DNS-based Global Server Load Balancing (GSLB)

This domain uses short TTLs across 4 record types (A record at 60s), consistent with DNS-based traffic management (GSLB). Enterprises operating large anycast networks intentionally use short TTLs to enable rapid failover, geographic steering, and load distribution. This is a deliberate infrastructure choice, not a misconfiguration. RFC 1035 §3.2.1 permits any TTL value the zone administrator selects. The findings below reflect deviation from typical values for reference, not necessarily actionable recommendations for this class of infrastructure.

The following DNS record TTLs deviate from typical values. For domains using DNS-based traffic management, short TTLs are expected and intentional.

Record Type Observed TTL Typical TTL Severity Context
TXT 250s 1 hour (3600s) high TXT TTL is below typical — observed 250s, 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 20045s 1 day (86400s) medium NS TTL is below typical — observed 20045s, 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.
MX 26s 1 hour (3600s) high MX TTL is below typical — observed 26s, 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.
AAAA 1 minute (60s) 1 hour (3600s) high AAAA TTL is below typical — observed 1 minute (60s), 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.
Provider Note: AWS Route 53 alias records have a fixed TTL of 60 seconds when pointing to AWS resources (ELB, CloudFront, S3). This is an AWS-specific extension, not part of DNS RFCs. To set a custom TTL, use a standard A/AAAA record or CNAME instead of an alias — but note this loses automatic IP tracking.
SOA 15 minutes (900s) 1 hour (3600s) medium SOA TTL is below typical — observed 15 minutes (900s), 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.
A 1 minute (60s) 1 hour (3600s) high A TTL is below typical — observed 1 minute (60s), 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.
Provider Note: AWS Route 53 alias records have a fixed TTL of 60 seconds when pointing to AWS resources (ELB, CloudFront, S3). This is an AWS-specific extension, not part of DNS RFCs. To set a custom TTL, use a standard A/AAAA record or CNAME instead of an alias — but note this loses automatic IP tracking.

Big Picture Questions

  • This domain runs short TTLs across multiple record types. Does it operate a global anycast network where DNS-based traffic steering justifies the query volume?
  • Are the short TTLs enabling active failover, geographic routing, or load distribution — or are they leftover from a migration that was never reverted?
  • Enterprise-grade DNS infrastructure (sub-5ms authoritative response times, globally distributed nameservers) absorbs short-TTL query volume. Would your authoritative DNS handle the same load?
Tune TTL for ui.com
Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) DNS provider detected: AWS Route 53 — provider-specific RFC compliance notes are shown inline above where applicable.
Primary NS ns-1849.awsdns-39.co.uk
Serial 1
Admin awsdns-hostmaster.amazon.com
Provider AWS Route 53
Timer Value RFC 1912 Range
Refresh7200s1,200–43,200s (20 min – 12 hrs)
Retry900sFraction of Refresh
Expire1209600s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)86400s300–86,400s (5 min – 1 day)
All SOA timer values are within RFC 1912 recommended ranges.

Independent RFC compliance assessment for AWS Route 53. Each finding cites the specific RFC section and reports what the engineering community consensus is. We report honestly — if a provider deviates from standards, we explain what they did differently and what the RFCs actually say.

Alias record TTLs fixed at 60s RFC 1035 §3.2.1

AWS Route 53 alias records pointing to AWS resources (ELB, CloudFront, S3, API Gateway) have a fixed TTL of 60 seconds that cannot be modified. Route 53 alias records are an AWS-specific extension — not part of standard DNS RFCs. They solve the CNAME-at-apex problem (RFC prohibits CNAME at zone apex) by appearing as A/AAAA records to resolvers. The 60-second TTL ensures fast failover but removes administrator TTL control.

Proprietary extension — not covered by DNS RFCs
This assessment is based on RFC specifications, provider documentation, and documented incidents from DNS engineering communities. DNS Tool does not have a commercial relationship with any provider listed.
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 44.8s, 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
Open
Configured
SPF (hard fail), DMARC (reject), DKIM, BIMI
Not Configured
MTA-STS, TLS-RPT, DNSSEC, CAA
Unavailable on Provider
DANE
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
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
Hostui.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.ui.com (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@ui.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.ui.com (MTA-STS policy record)
Valuev=STSv1; id=ui.com
RFC 8461
Open Remediation Workspace — Copy-Paste Ready Records
Registrar (RDAP) OBSERVED LIVE
GoDaddy.com, LLC
Where domain was purchased
Email Service Provider INFERRED
Google Workspace
Strongly Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting OBSERVED
Amazon Route 53
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 Consistent

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

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

v=spf1 include:_spf.google.com include:mail.zendesk.com include:amazonses.com include:spf1.mcsv.net include:shops.shopify.com include:mailsenders.netsuite.com -all
RFC 7489: -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 Consistent

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

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject; aspf=r; adkim=s; sp=quarantine; rua=mailto:dmarc-reports@ui.com
Alignment: SPF relaxed DKIM strict sp=quarantine
No forensic reporting (ruf) tag — this is correct. The absence of ruf= is not a gap. 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 regardless. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification, confirming its deprecation. Omitting ruf= is the recommended modern practice. 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 Consistent

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

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

google._domainkey Google Workspace 2048-bit Adequate
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCRpbqA2Kb2lxNrA1kmhnfArmiFoseRwXXj6O+X4Vg6rSqDsOighmCmYBJWrVyfDzWkUzXai7w2ob5lHwvzgx1lGVmN59vXmIg3Vo0dMapzCRTo41SVZcHbuqFIwbYb2XVC4vYVWsGTQz9TNQ9Qh0/Us3yESb6CkrDIwBzErLX1iQIDAQAB
k2._domainkey MailChimp 2048-bit Adequate
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey MailChimp 2048-bit Adequate
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
mandrill._domainkey MailChimp (Mandrill) 2048-bit Adequate
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
zendesk1._domainkey Zendesk 2048-bit Adequate
v=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB
zendesk2._domainkey Zendesk 2048-bit Adequate
v=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aOaPONDZWHv027rkiGIwb838OyXPgvFDEkCV/qGcdXSjZnaVAadrTm/oKnL8WOltP9zB1FLEuKt0fTi5zRyKPE4oIYCnEzXwrGqzjUcCABQBawQVqvXjDOaYh9Lhp8W5PYOLo905vRW7ipyIMDhuzBOJls91/WWXnNK0OwP3RghiisZjA3K2KqtRwf7w6GjNeNuAMNhvcmgAN15d/mhK+dev/hcRbal66RoYyTD8c0F0isahWH0envEX8aj+SBhheNk0/U37dGE+4nFaY5yP9CUlYjFKDSIKZgHzG4Hci3t/RubU58pi6BCrQQdAFvIOeDFeCZ0ywIDAQAB
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 Consistent

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 Consistent

Will failures in TLS delivery be reported? No reporting
Warning

No TLS-RPT record found

DANE / TLSA Consistent Recon Methodology Can mail servers establish identity without a public CA? No
RFC 7672 §3 RFC 6698 §2 Not Available

DANE not available — Google Workspace does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Google Workspace

Google Workspace supports DANE for outbound mail verification but does not publish TLSA records for its MX hosts.

Recommended alternative: MTA-STS

Note: Google Workspace does validate DANE/TLSA when sending mail to DANE-enabled recipients (outbound DANE).

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 Google Workspace 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? Unlikely DMARC reject policy blocks email spoofing (RFC 7489 §6.3) and BIMI with VMC provides verified brand identity in inboxes — email-based brand faking is effectively blocked; adding CAA records (RFC 8659) would further restrict certificate issuance for lookalike domains

BIMI BIMI Spec Consistent 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://files.svc.ui.com/it/logos/ubiquiti_inc_logo_01_12_2025.svg; a=https://files.svc.ui.com/it/certificates/ubiquiti_inc_01_12_2025.pem;
BIMI Logo
Logo validated (SVG) View full logo

CAA RFC 8659 §4 Consistent 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? Partial RFC 9116

security.txt found with issues

Contact

security@ui.com

Expires

Missing (required by RFC 9116 §2.5.5)

Encryption

https://ui.com/support/security-rewards/pgp-key/

Policy

https://ui.com/security/
Source: https://ui.com/.well-known/security.txt
Missing required Expires field (RFC 9116 §2.5.5)
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 View 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.
Sources scanned (2)
  • http://ui.com/
  • https://ui.com/microsite/static/index-CWqBoZ7O.js
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 ns-1469.awsdns-55.org — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.

Check Result Detail
Zone Transfer (AXFR) Denied Zone transfer denied (correct configuration)
Open Recursion Disabled Recursion disabled (correct configuration)
Nameserver Identity Hidden No nameserver identity information disclosed
Cache Snooping Protected Cache snooping not possible (correct configuration)

Tested nameservers: ns-1469.awsdns-55.org, ns-656.awsdns-18.net, ns-277.awsdns-34.com, ns-1849.awsdns-39.co.uk

Delegation Consistency 1 Issue

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

Findings:
  • Could not retrieve NS TTL from parent zone

DS ↔ DNSKEY Alignment Aligned

Glue Record Completeness Complete

NameserverIn-BailiwickIPv4 GlueIPv6 GlueStatus
ns-1469.awsdns-55.org No N/A N/A OK
ns-1849.awsdns-39.co.uk No N/A N/A OK
ns-277.awsdns-34.com No N/A N/A OK
ns-656.awsdns-18.net No N/A N/A OK

NS TTL Comparison Drift

Child TTL: 172800s Drift: 0s

SOA Serial Consistency Consistent

ns-1469.awsdns-55.org: 1
ns-1849.awsdns-39.co.uk: 1
ns-277.awsdns-34.com: 1
ns-656.awsdns-18.net: 1
Nameserver Fleet Matrix Healthy

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

Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial
ns-277.awsdns-34.com 205.251.193.21 2600:9000:5301:1500::1 AS16509
Amazon.com, Inc. 		1
ns-1849.awsdns-39.co.uk 205.251.199.57 2600:9000:5307:3900::1 AS16509
Amazon.com, Inc. 		1
ns-1469.awsdns-55.org 205.251.197.189 2600:9000:5305:bd00::1 AS16509
Amazon.com, Inc. 		1
ns-656.awsdns-18.net 205.251.194.144 2600:9000:5302:9000::1 AS16509
Amazon.com, Inc. 		1
Unique ASNs
1
Unique Operators
1
Unique /24 Prefixes
4
Diversity Score
Fair

1 ASN(s), 4 /24 prefix(es) — consider adding diversity

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

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

Policy Assessment Primary
  • Google Workspace enforces TLS 1.2+ with valid certificates on all inbound/outbound mail
Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
Skipped — Remote probe failed (connection failed — probe may be offline) and local port 25 is blocked. Transport security is assessed via DNS policy records per NIST SP 800-177 Rev. 1.
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

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

IPv4 Mappings:
18.172.134.102 → AS ()
18.172.134.21 → AS ()
18.172.134.68 → AS ()
18.172.134.72 → AS ()
IPv6 Mappings:
2600:9000:24bf:4800:1c:894d:51c0:93a1 → AS ()
2600:9000:24bf:6000:1c:894d:51c0:93a1 → AS ()
2600:9000:24bf:6400:1c:894d:51c0:93a1 → AS ()
2600:9000:24bf:8e00:1c:894d:51c0:93a1 → AS ()
2600:9000:24bf:d200:1c:894d:51c0:93a1 → AS ()
2600:9000:24bf:e400:1c:894d:51c0:93a1 → AS ()
2600:9000:24bf:f400:1c:894d:51c0:93a1 → AS ()
2600:9000:24bf:fe00:1c:894d:51c0:93a1 → AS ()

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
Microsoft 365 MS=ms52865930
Apple apple-domain-verification=uyOWs9cUCcTU0jeH
Atlassian atlassian-domain-verification=lAbFoCTHsRb93t2z/FwrfYtXYGp7fvE2B062vMTFkttMmh+7wI...
Facebook / Meta facebook-domain-verification=6vwegmc13do3c4xtsd6q81h3wg7c20
Google Workspace google-site-verification=nNgyKTT_jHbEdL0fm7ix1Jq-7lRGa10u7Bm3hH5AnYc
Miro miro-verification=d941df6f08d6c13ec000ae219dd87ce1431c9c1f
Slack slack-domain-verification=8EBuKYor1ScaV9ELrvX4K5nZuqbtogpBd46bsUY4
Stripe stripe-verification=329824bab081048c274832f2e4f67bc207cf462009618b0ead129985cb7f...
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 Consistent 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: ns-1469.awsdns-55.org ns-1849.awsdns-39.co.uk ns-277.awsdns-34.com ns-656.awsdns-18.net
Managed DNS
All 4 nameservers hosted by Amazon Route 53. Managed DNS provides reliable resolution with provider-maintained infrastructure.
DNS provider(s): Amazon Route 53
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (3 differences found)
Resolver Differences:
A: DNS4EU returned different results: [18.239.36.19 18.239.36.21 18.239.36.55 18.239.36.81]
A: Quad9 returned different results: [18.160.143.125 18.160.143.126 18.160.143.7 18.160.143.77]
TXT: OpenDNS returned different results: [8f 89 8a 22 27 bd 7c a9 9e 94 MS=ms52865930 ZOOM_verify_XRDIBHQhSMywYeoY27cjaw apple-domain-verification=uyOWs9cUCcTU0jeH docker-verification=99a15296-81f6-45a8-b375-3764882eb726 miro-verification=d941df6f08d6c13ec000ae219dd87ce1431c9c1f openai-domain-verification=dv-x2kAmnTrpB3PWbhPp7TBhNK8 parsec-domain-verification=td_2tEeYJdjd0wuOv2cOJDSbK3Rl0V]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

18.172.134.102
18.172.134.21
18.172.134.68
18.172.134.72
Where the domain points for web traffic

AAAAIPv6 Address

2600:9000:24bf:4800:1c:894d:51c0:93a1
2600:9000:24bf:6000:1c:894d:51c0:93a1
2600:9000:24bf:6400:1c:894d:51c0:93a1
2600:9000:24bf:8e00:1c:894d:51c0:93a1
2600:9000:24bf:d200:1c:894d:51c0:93a1
2600:9000:24bf:e400:1c:894d:51c0:93a1
2600:9000:24bf:f400:1c:894d:51c0:93a1
2600:9000:24bf:fe00:1c:894d:51c0:93a1
IPv6 ready

MXMail Servers

1 aspmx.l.google.com.
10 aspmx2.googlemail.com.
10 aspmx3.googlemail.com.
5 alt1.aspmx.l.google.com.
5 alt2.aspmx.l.google.com.
Priority + mail server for email delivery
Google Workspace

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (4 IPv4, 8 IPv6) Mail: 5 servers Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 507 subdomains discovered
How did we find these?
Certificate Transparency Logs Unavailable The results below are from DNS probing only and may be significantly incomplete. CT logs typically reveal hundreds or thousands of additional subdomains via certificate issuance history (RFC 6962).
Re-Analyze to Retry CT Lookup
CT logs unavailable 507 current 0 expired 4 CNAMEs Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
a.ui.com DNS Current — — — —
academy.ui.com DNS Current — — — —
account.ui.com DNS Current — — — —
accounting.ui.com DNS Current — — — —
accounts.ui.com DNS Current — — — —
ad.ui.com DNS Current — — — —
adfs.ui.com DNS Current — — — —
admin.ui.com DNS Current — — — —
admin1.ui.com DNS Current — — — —
admin2.ui.com DNS Current — — — —
alert.ui.com DNS Current — — — —
alerts.ui.com DNS Current — — — —
alpha.ui.com DNS Current — — — —
analytics.ui.com DNS Current — — — —
ap-south.ui.com DNS Current — — — —
ap.ui.com DNS Current — — — —
apac.ui.com DNS Current — — — —
api.ui.com DNS Current — — — —
api1.ui.com DNS Current — — — —
api2.ui.com DNS Current — — — —
api3.ui.com DNS Current — — — —
apigw.ui.com DNS Current — — — —
apis.ui.com DNS Current — — — —
apm.ui.com DNS Current — — — —
app.ui.com DNS Current — — — —
app1.ui.com DNS Current — — — —
app2.ui.com DNS Current — — — —
appointments.ui.com DNS Current — — — —
apps.ui.com DNS Current — — — —
archive.ui.com DNS Current — — — —
archives.ui.com DNS Current — — — —
assets.ui.com DNS Current — — — —
atom.ui.com DNS Current — — — —
auth.ui.com DNS Current — — — —
auth0.ui.com DNS Current — — — —
autoconfig.ui.com DNS Current — — — —
autodiscover.ui.com DNS Current — — — —
b.ui.com DNS Current — — — —
backup.ui.com DNS Current — — — —
backup1.ui.com DNS Current — — — —
backup2.ui.com DNS Current — — — —
beta.ui.com DNS Current — — — —
bi.ui.com DNS Current — — — —
bigdata.ui.com DNS Current — — — —
billing.ui.com DNS Current — — — —
bitbucket.ui.com DNS Current — — — —
blob.ui.com DNS Current — — — —
blog.ui.com DNS Current — — — —
booking.ui.com DNS Current — — — —
broker.ui.com DNS Current — — — —
bucket.ui.com DNS Current — — — —
build.ui.com DNS Current — — — —
builds.ui.com DNS Current — — — —
c.ui.com DNS Current — — — —
ca.ui.com DNS Current — — — —
cache.ui.com DNS Current — — — —
cal.ui.com DNS Current — — — —
calendar.ui.com DNS Current — — — —
campaign.ui.com DNS Current — — — —
campaigns.ui.com DNS Current — — — —
careers.ui.com DNS Current — — — —
cart.ui.com DNS Current — — — —
catalog.ui.com DNS Current — — — —
cd.ui.com DNS Current — — — —
cdn.ui.com DNS Current — — — —
cdn1.ui.com DNS Current — — — —
cdn2.ui.com DNS Current — — — —
cdn3.ui.com DNS Current — — — —
cert.ui.com DNS Current — — — —
certs.ui.com DNS Current — — — —
chat.ui.com DNS Current — — — —
checkout.ui.com DNS Current — — — —
ci.ui.com DNS Current — — — —
client.ui.com DNS Current — — — —
clients.ui.com DNS Current — — — —
cloud.ui.com DNS Current — — — —
cms.ui.com DNS Current — — — —
cname.ui.com DNS Current — — — —
code.ui.com DNS Current — — — —
community.ui.com DNS Current — — — —
compliance.ui.com DNS Current — — — —
conference.ui.com DNS Current — — — —
config.ui.com DNS Current — — — —
configuration.ui.com DNS Current — — — —
confluence.ui.com DNS Current — — — —
connect.ui.com DNS Current — — — —
console.ui.com DNS Current — — — —
containers.ui.com DNS Current — — — —
content.ui.com DNS Current — — — —
corp.ui.com DNS Current — — — —
corporate.ui.com DNS Current — — — —
courses.ui.com DNS Current — — — —
cpanel.ui.com DNS Current — — — —
crl.ui.com DNS Current — — — —
crm.ui.com DNS Current — — — —
d.ui.com DNS Current — — — —
dashboard.ui.com DNS Current — — — —
data.ui.com DNS Current — — — —
data1.ui.com DNS Current — — — —
data2.ui.com DNS Current — — — —
database.ui.com DNS Current — — — —
datadog.ui.com DNS Current — — — —
db.ui.com DNS Current — — — —
db1.ui.com DNS Current — — — —
db2.ui.com DNS Current — — — —
dedicated.ui.com DNS Current — — — —
demo.ui.com DNS Current — — — —
deploy.ui.com DNS Current — — — —
deployment.ui.com DNS Current — — — —
dev.ui.com DNS Current — — — —
dev1.ui.com DNS Current — — — —
dev2.ui.com DNS Current — — — —
develop.ui.com DNS Current — — — —
developer.ui.com DNS Current — — — —
developers.ui.com DNS Current — — — —
devices.ui.com DNS Current — — — —
devops.ui.com DNS Current — — — —
directory.ui.com DNS Current — — — —
discuss.ui.com DNS Current — — — —
discussions.ui.com DNS Current — — — —
dns.ui.com DNS Current — — — —
dns1.ui.com DNS Current — — — —
dns2.ui.com DNS Current — — — —
dnscheck.ui.com DNS Current — — — —
dnstool.ui.com DNS Current — — — —
doc.ui.com DNS Current — — — —
docker.ui.com DNS Current — — — —
docs.ui.com DNS Current — — — —
documentation.ui.com DNS Current — — — —
download.ui.com DNS Current — — — —
downloads.ui.com DNS Current — — — —
drupal.ui.com DNS Current — — — —
e.ui.com DNS Current — — — —
ecommerce.ui.com DNS Current — — — —
edge.ui.com DNS Current — — — —
edge1.ui.com DNS Current — — — —
edge2.ui.com DNS Current — — — —
education.ui.com DNS Current — — — —
elastic.ui.com DNS Current — — — —
elasticsearch.ui.com DNS Current — — — —
email.ui.com DNS Current — — — —
emea.ui.com DNS Current — — — —
endpoint.ui.com DNS Current — — — —
erp.ui.com DNS Current — — — —
es.ui.com DNS Current — — — —
etl.ui.com DNS Current — — — —
eu-west.ui.com DNS Current — — — —
eu.ui.com DNS Current — — — —
event.ui.com DNS Current — — — —
events.ui.com DNS Current — — — —
exchange.ui.com DNS Current — — — —
ext.ui.com DNS Current — — — —
f.ui.com DNS Current — — — —
faq.ui.com DNS Current — — — —
feed.ui.com DNS Current — — — —
feedback.ui.com DNS Current — — — —
feeds.ui.com DNS Current — — — —
file.ui.com DNS Current — — — —
files.ui.com DNS Current — — — —
finance.ui.com DNS Current — — — —
firewall.ui.com DNS Current — — — —
forms.ui.com DNS Current — — — —
forum.ui.com DNS Current — — — —
forums.ui.com DNS Current — — — —
ftp.ui.com DNS Current — — — —
ftp1.ui.com DNS Current — — — —
ftp2.ui.com DNS Current — — — —
fw.ui.com DNS Current — — — —
gateway.ui.com DNS Current — — — —
geo.ui.com DNS Current — — — —
gis.ui.com DNS Current — — — —
git.ui.com DNS Current — — — —
github.ui.com DNS Current — — — —
gitlab.ui.com DNS Current — — — —
go.ui.com DNS Current — — — —
grafana.ui.com DNS Current — — — —
graphql.ui.com DNS Current — — — —
gw.ui.com DNS Current — — — —
gw1.ui.com DNS Current — — — —
gw2.ui.com DNS Current — — — —
haproxy.ui.com DNS Current — — — —
health.ui.com DNS Current — — — —
healthcheck.ui.com DNS Current — — — —
help.ui.com DNS Current ubnt.zendesk.com — — —
helpdesk.ui.com DNS Current — — — —
hiring.ui.com DNS Current — — — —
host.ui.com DNS Current — — — —
hosting.ui.com DNS Current — — — —
hq.ui.com DNS Current — — — —
hr.ui.com DNS Current — — — —
hris.ui.com DNS Current — — — —
hub.ui.com DNS Current — — — —
id.ui.com DNS Current — — — —
identity.ui.com DNS Current — — — —
image.ui.com DNS Current — — — —
images.ui.com DNS Current — — — —
imap.ui.com DNS Current — — — —
img.ui.com DNS Current — — — —
int.ui.com DNS Current — — — —
internal.ui.com DNS Current — — — —
intranet.ui.com DNS Current — — — —
inventory.ui.com DNS Current — — — —
investor.ui.com DNS Current — — — —
investors.ui.com DNS Current — — — —
invoice.ui.com DNS Current — — — —
ir.ui.com DNS Current ubiquiti-ir.prod-mid-euw3.investis.com — — —
it.ui.com DNS Current — — — —
itsm.ui.com DNS Current — — — —
itsupport.ui.com DNS Current — — — —
jenkins.ui.com DNS Current — — — —
jira.ui.com DNS Current — — — —
jobs.ui.com DNS Current — — — —
k8s.ui.com DNS Current — — — —
kafka.ui.com DNS Current — — — —
kb.ui.com DNS Current — — — —
kibana.ui.com DNS Current — — — —
kong.ui.com DNS Current — — — —
kubernetes.ui.com DNS Current — — — —
lab.ui.com DNS Current — — — —
labs.ui.com DNS Current — — — —
lan.ui.com DNS Current — — — —
lb.ui.com DNS Current — — — —
ldap.ui.com DNS Current — — — —
learn.ui.com DNS Current — — — —
learning.ui.com DNS Current — — — —
legal.ui.com DNS Current — — — —
link.ui.com DNS Current — — — —
links.ui.com DNS Current — — — —
live.ui.com DNS Current — — — —
lms.ui.com DNS Current — — — —
loadbalancer.ui.com DNS Current — — — —
location.ui.com DNS Current — — — —
log.ui.com DNS Current — — — —
login.ui.com DNS Current — — — —
logs.ui.com DNS Current — — — —
lookup.ui.com DNS Current — — — —
m.ui.com DNS Current — — — —
mail.ui.com DNS Current — — — —
mail1.ui.com DNS Current — — — —
mail2.ui.com DNS Current — — — —
mail3.ui.com DNS Current — — — —
mailgw.ui.com DNS Current — — — —
mailhost.ui.com DNS Current — — — —
mailrelay.ui.com DNS Current — — — —
mailserver.ui.com DNS Current — — — —
manage.ui.com DNS Current — — — —
management.ui.com DNS Current — — — —
manager.ui.com DNS Current — — — —
map.ui.com DNS Current — — — —
maps.ui.com DNS Current — — — —
marketing.ui.com DNS Current — — — —
mdm.ui.com DNS Current — — — —
media.ui.com DNS Current — — — —
meet.ui.com DNS Current — — — —
meeting.ui.com DNS Current — — — —
memcached.ui.com DNS Current — — — —
metrics.ui.com DNS Current — — — —
microservices.ui.com DNS Current — — — —
mobile.ui.com DNS Current — — — —
mongo.ui.com DNS Current — — — —
mongodb.ui.com DNS Current — — — —
monitor.ui.com DNS Current — — — —
monitoring.ui.com DNS Current — — — —
mq.ui.com DNS Current — — — —
mta.ui.com DNS Current — — — —
mx.ui.com DNS Current — — — —
mx1.ui.com DNS Current — — — —
mx2.ui.com DNS Current — — — —
mx3.ui.com DNS Current — — — —
mx4.ui.com DNS Current — — — —
mx5.ui.com DNS Current — — — —
mxtoolbox.ui.com DNS Current — — — —
my.ui.com DNS Current — — — —
myaccount.ui.com DNS Current — — — —
mysql.ui.com DNS Current — — — —
na.ui.com DNS Current — — — —
nagios.ui.com DNS Current — — — —
net.ui.com DNS Current — — — —
netadmin.ui.com DNS Current — — — —
nettool.ui.com DNS Current — — — —
nettools.ui.com DNS Current — — — —
network.ui.com DNS Current — — — —
news.ui.com DNS Current — — — —
nginx.ui.com DNS Current — — — —
node1.ui.com DNS Current — — — —
node2.ui.com DNS Current — — — —
node3.ui.com DNS Current — — — —
notify.ui.com DNS Current — — — —
ns.ui.com DNS Current — — — —
ns1.ui.com DNS Current — — — —
ns2.ui.com DNS Current — — — —
ns3.ui.com DNS Current — — — —
ns4.ui.com DNS Current — — — —
ns5.ui.com DNS Current — — — —
ns6.ui.com DNS Current — — — —
o365.ui.com DNS Current — — — —
oauth.ui.com DNS Current — — — —
object.ui.com DNS Current — — — —
ocsp.ui.com DNS Current — — — —
office.ui.com DNS Current — — — —
okta.ui.com DNS Current — — — —
order.ui.com DNS Current — — — —
orders.ui.com DNS Current — — — —
origin.ui.com DNS Current — — — —
origin1.ui.com DNS Current — — — —
origin2.ui.com DNS Current — — — —
outlook.ui.com DNS Current — — — —
owa.ui.com DNS Current — — — —
panel.ui.com DNS Current — — — —
partner.ui.com DNS Current — — — —
partners.ui.com DNS Current — — — —
pay.ui.com DNS Current — — — —
payment.ui.com DNS Current — — — —
payments.ui.com DNS Current — — — —
payroll.ui.com DNS Current — — — —
pbx.ui.com DNS Current — — — —
phone.ui.com DNS Current — — — —
photos.ui.com DNS Current — — — —
pingdom.ui.com DNS Current — — — —
pki.ui.com DNS Current — — — —
plesk.ui.com DNS Current — — — —
policies.ui.com DNS Current — — — —
policy.ui.com DNS Current — — — —
pop.ui.com DNS Current — — — —
pop3.ui.com DNS Current — — — —
portal.ui.com DNS Current — — — —
portal2.ui.com DNS Current — — — —
postgres.ui.com DNS Current — — — —
pre.ui.com DNS Current — — — —
preprod.ui.com DNS Current — — — —
press.ui.com DNS Current — — — —
preview.ui.com DNS Current — — — —
primary.ui.com DNS Current — — — —
print.ui.com DNS Current — — — —
printer.ui.com DNS Current — — — —
privacy.ui.com DNS Current — — — —
private.ui.com DNS Current — — — —
product.ui.com DNS Current — — — —
products.ui.com DNS Current — — — —
profile.ui.com DNS Current — — — —
prometheus.ui.com DNS Current — — — —
promo.ui.com DNS Current — — — —
proxy.ui.com DNS Current — — — —
proxy1.ui.com DNS Current — — — —
proxy2.ui.com DNS Current — — — —
public.ui.com DNS Current — — — —
qa.ui.com DNS Current — — — —
queue.ui.com DNS Current — — — —
r.ui.com DNS Current — — — —
ra.ui.com DNS Current — — — —
rabbitmq.ui.com DNS Current — — — —
rancher.ui.com DNS Current — — — —
realtime.ui.com DNS Current — — — —
recruit.ui.com DNS Current — — — —
redirect.ui.com DNS Current — — — —
redis.ui.com DNS Current — — — —
register.ui.com DNS Current — — — —
registry.ui.com DNS Current — — — —
relay.ui.com DNS Current — — — —
relay1.ui.com DNS Current — — — —
releases.ui.com DNS Current — — — —
remote.ui.com DNS Current — — — —
repo.ui.com DNS Current — — — —
report.ui.com DNS Current — — — —
reporting.ui.com DNS Current — — — —
reports.ui.com DNS Current — — — —
repos.ui.com DNS Current — — — —
reservations.ui.com DNS Current — — — —
rest.ui.com DNS Current — — — —
rss.ui.com DNS Current — — — —
rt.ui.com DNS Current — — — —
s3.ui.com DNS Current — — — —
sandbox.ui.com DNS Current — — — —
sandbox1.ui.com DNS Current — — — —
sandbox2.ui.com DNS Current — — — —
scan.ui.com DNS Current — — — —
scanner.ui.com DNS Current — — — —
schedule.ui.com DNS Current — — — —
scp.ui.com DNS Current — — — —
search.ui.com DNS Current — — — —
secondary.ui.com DNS Current — — — —
secrets.ui.com DNS Current — — — —
secure.ui.com DNS Current — — — —
server.ui.com DNS Current — — — —
server1.ui.com DNS Current — — — —
server2.ui.com DNS Current — — — —
server3.ui.com DNS Current — — — —
service.ui.com DNS Current — — — —
servicedesk.ui.com DNS Current — — — —
services.ui.com DNS Current — — — —
sftp.ui.com DNS Current — — — —
share.ui.com DNS Current — — — —
shop.ui.com DNS Current — — — —
signin.ui.com DNS Current — — — —
signup.ui.com DNS Current — — — —
sip.ui.com DNS Current — — — —
slack.ui.com DNS Current — — — —
smtp.ui.com DNS Current — — — —
smtp1.ui.com DNS Current — — — —
smtp2.ui.com DNS Current — — — —
socket.ui.com DNS Current — — — —
solr.ui.com DNS Current — — — —
speedtest.ui.com DNS Current — — — —
sql.ui.com DNS Current — — — —
srv.ui.com DNS Current — — — —
srv1.ui.com DNS Current — — — —
srv2.ui.com DNS Current — — — —
ssh.ui.com DNS Current — — — —
ssl.ui.com DNS Current — — — —
sso.ui.com DNS Current — — — —
stage.ui.com DNS Current — — — —
staging.ui.com DNS Current — — — —
static.ui.com DNS Current — — — —
static1.ui.com DNS Current — — — —
static2.ui.com DNS Current — — — —
statistics.ui.com DNS Current — — — —
stats.ui.com DNS Current — — — —
status.ui.com DNS Current r9sjd13s1zsp.stspg-customer.com — — —
statuspage.ui.com DNS Current — — — —
stg.ui.com DNS Current — — — —
storage.ui.com DNS Current — — — —
store.ui.com DNS Current — — — —
stream.ui.com DNS Current — — — —
streaming.ui.com DNS Current — — — —
support.ui.com DNS Current — — — —
support2.ui.com DNS Current — — — —
surveys.ui.com DNS Current — — — —
svn.ui.com DNS Current — — — —
swift.ui.com DNS Current — — — —
sysadmin.ui.com DNS Current — — — —
syslog.ui.com DNS Current — — — —
talent.ui.com DNS Current — — — —
teams.ui.com DNS Current — — — —
techsupport.ui.com DNS Current — — — —
tel.ui.com DNS Current — — — —
telecom.ui.com DNS Current — — — —
terms.ui.com DNS Current — — — —
test.ui.com DNS Current — — — —
test1.ui.com DNS Current — — — —
test2.ui.com DNS Current — — — —
testing.ui.com DNS Current — — — —
ticket.ui.com DNS Current — — — —
tickets.ui.com DNS Current — — — —
tls.ui.com DNS Current — — — —
tool.ui.com DNS Current — — — —
tools.ui.com DNS Current — — — —
trace.ui.com DNS Current — — — —
tracing.ui.com DNS Current — — — —
tracking.ui.com DNS Current — — — —
training.ui.com DNS Current saas.moonami.com — — —
uat.ui.com DNS Current — — — —
upload.ui.com DNS Current — — — —
uploads.ui.com DNS Current — — — —
uptime.ui.com DNS Current — — — —
url.ui.com DNS Current — — — —
us-east.ui.com DNS Current — — — —
us-west.ui.com DNS Current — — — —
us.ui.com DNS Current — — — —
utility.ui.com DNS Current — — — —
varnish.ui.com DNS Current — — — —
vault.ui.com DNS Current — — — —
vendor.ui.com DNS Current — — — —
vendors.ui.com DNS Current — — — —
video.ui.com DNS Current — — — —
videos.ui.com DNS Current — — — —
voip.ui.com DNS Current — — — —
vpn.ui.com DNS Current — — — —
vpn1.ui.com DNS Current — — — —
vpn2.ui.com DNS Current — — — —
vpn3.ui.com DNS Current — — — —
vps.ui.com DNS Current — — — —
waf.ui.com DNS Current — — — —
wan.ui.com DNS Current — — — —
warehouse.ui.com DNS Current — — — —
web.ui.com DNS Current — — — —
web1.ui.com DNS Current — — — —
web2.ui.com DNS Current — — — —
webapi.ui.com DNS Current — — — —
webapp.ui.com DNS Current — — — —
webex.ui.com DNS Current — — — —
webhost.ui.com DNS Current — — — —
webinar.ui.com DNS Current — — — —
webinars.ui.com DNS Current — — — —
webmail.ui.com DNS Current — — — —
webproxy.ui.com DNS Current — — — —
webserver.ui.com DNS Current — — — —
websocket.ui.com DNS Current — — — —
webtool.ui.com DNS Current — — — —
webtools.ui.com DNS Current — — — —
whm.ui.com DNS Current — — — —
whois.ui.com DNS Current — — — —
wiki.ui.com DNS Current — — — —
wordpress.ui.com DNS Current — — — —
work.ui.com DNS Current — — — —
worker.ui.com DNS Current — — — —
worker1.ui.com DNS Current — — — —
worker2.ui.com DNS Current — — — —
workspace.ui.com DNS Current — — — —
wp.ui.com DNS Current — — — —
ws.ui.com DNS Current — — — —
www.ui.com DNS Current — — — —
www1.ui.com DNS Current — — — —
www2.ui.com DNS Current — — — —
www3.ui.com DNS Current — — — —
xml.ui.com DNS Current — — — —
zabbix.ui.com DNS Current — — — —
zoom.ui.com DNS Current — — — —
Export Recon (CSV)
Δ Changes Detected: AAAA 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 4 / 4 records
18.172.134.102
18.172.134.72
18.172.134.21
18.172.134.21
18.172.134.68
18.172.134.68
18.172.134.72
18.172.134.102
AAAA Propagating 8 / 8 records
2600:9000:24bf:4800:1c:894d:51c0:93a1
2600:9000:24bf:9000:1c:894d:51c0:93a1
2600:9000:24bf:6000:1c:894d:51c0:93a1
2600:9000:24bf:3000:1c:894d:51c0:93a1
2600:9000:24bf:6400:1c:894d:51c0:93a1
2600:9000:24bf:6800:1c:894d:51c0:93a1
2600:9000:24bf:8e00:1c:894d:51c0:93a1
2600:9000:24bf:d200:1c:894d:51c0:93a1
2600:9000:24bf:d200:1c:894d:51c0:93a1
2600:9000:24bf:ee00:1c:894d:51c0:93a1
2600:9000:24bf:e400:1c:894d:51c0:93a1
2600:9000:24bf:5e00:1c:894d:51c0:93a1
2600:9000:24bf:f400:1c:894d:51c0:93a1
2600:9000:24bf:d800:1c:894d:51c0:93a1
2600:9000:24bf:fe00:1c:894d:51c0:93a1
2600:9000:24bf:4000:1c:894d:51c0:93a1
CAA RFC 8659 §4 0 / 0 records
No records
No records
DMARC _dmarc.ui.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject; aspf=r; adkim=s; sp=quarantine; rua=mailto:dmarc-reports@ui.com
v=DMARC1; p=reject; aspf=r; adkim=s; sp=quarantine; rua=mailto:dmarc-reports@ui.com
MX RFC 5321 Synchronized 5 / 5 records
1 aspmx.l.google.com.
1 aspmx.l.google.com.
10 aspmx2.googlemail.com.
10 aspmx2.googlemail.com.
10 aspmx3.googlemail.com.
10 aspmx3.googlemail.com.
5 alt1.aspmx.l.google.com.
5 alt1.aspmx.l.google.com.
5 alt2.aspmx.l.google.com.
5 alt2.aspmx.l.google.com.
NS RFC 1035 Synchronized 4 / 4 records
ns-1469.awsdns-55.org.
ns-1469.awsdns-55.org.
ns-1849.awsdns-39.co.uk.
ns-1849.awsdns-39.co.uk.
ns-277.awsdns-34.com.
ns-277.awsdns-34.com.
ns-656.awsdns-18.net.
ns-656.awsdns-18.net.
SOA RFC 1035 Synchronized 1 / 1 records
ns-1849.awsdns-39.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
ns-1849.awsdns-39.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
TXT RFC 7208 §4 25 / 0 records
8f 89 8a 22 27 bd 7c a9 9e 94
—
MS=ms52865930
—
ZOOM_verify_XRDIBHQhSMywYeoY27cjaw
—
anthropic-domain-verification-ve2d7z=0Eo6cOQIi0eUfhUO7JlJTwtdV
—
apple-domain-verification=uyOWs9cUCcTU0jeH
—
atlassian-domain-verification=lAbFoCTHsRb93t2z/FwrfYtXYGp7fvE2B062vMTFkttMmh+7wI9GlRruCceCcUvQ
—
cursor-domain-verification-3wqvzt=JlQso9344JMrA7q8pwVZlEwad
—
docker-verification=99a15296-81f6-45a8-b375-3764882eb726
—
facebook-domain-verification=6vwegmc13do3c4xtsd6q81h3wg7c20
—
google-site-verification=nNgyKTT_jHbEdL0fm7ix1Jq-7lRGa10u7Bm3hH5AnYc
—
google-site-verification=yNXLmtMVTPDcqBxMofZjGGRh2_fjznkswT77X9CiCNU
—
h1-domain-verification=XjxXt7rm2dbAPoU4DtJnBMPQj5Jn3NvtNNVcCHuxjPS9QVPB
—
miro-verification=d941df6f08d6c13ec000ae219dd87ce1431c9c1f
—
onetrust-domain-verification=ef8b17a80e3140198201846711440b42
—
openai-domain-verification=dv-x2kAmnTrpB3PWbhPp7TBhNK8
—
parsec-domain-verification=td_2tEeYJdjd0wuOv2cOJDSbK3Rl0V
—
slack-domain-verification=8EBuKYor1ScaV9ELrvX4K5nZuqbtogpBd46bsUY4
—
stripe-verification=329824bab081048c274832f2e4f67bc207cf462009618b0ead129985cb7f708b
—
stripe-verification=4ca76301ce7d0aebc38ad3bdd06174739c5de9fc2865de17249e1600698a5b12
—
stripe-verification=b5087fe77e9f8d360da3e37a39ffb5a55ebcc5f65f093d9b9e70d322c57f3261
—
stripe-verification=d1a805b456513daefa7f162a7737b5a0c2282986b392af4fb02b36e567950c4c
—
stripe-verification=f3757f1e7e108518555c378da265fa046d2380175ebe4cc24053d4f77eb9f604
—
teamviewer-sso-verification=8a374dd1a3e3400ba2cbaaba66911053
—
v=spf1 include:_spf.google.com include:mail.zendesk.com include:amazonses.com include:spf1.mcsv.net include:shops.shopify.com include:mailsenders.netsuite.com -all
—
zapier-domain-verification-challenge=725b5c64-8b2e-4805-aaa9-d6fa3c0d65c4
—
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.

1d886c366013c293edc42a9ad2a101cfa685ed9babfca89e3759a77191f94be740beaf5e5d46b4bff402de8e2e32718dd5dac53cd379fdc10de5466a290a0419
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 22 Apr 2026, 14:06 UTC.
Download Raw Intelligence Download Checksum (.sha3) Cross-Reference Verification

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-ui.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-ui.com.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-ui.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-ui.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/15240/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 ui.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 ui.com A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer ui.com AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer ui.com MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer ui.com NS
Query TXT records RFC 1035 
dig +noall +answer ui.com TXT

Email Authentication

Check SPF record RFC 7208 
dig +short ui.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.ui.com TXT
Check DKIM key for selector 'google' RFC 6376 
dig +short google._domainkey.ui.com TXT
Check DKIM key for selector 'k2' RFC 6376 
dig +short k2._domainkey.ui.com TXT
Check DKIM key for selector 'k3' RFC 6376 
dig +short k3._domainkey.ui.com TXT
Check DKIM key for selector 'mandrill' RFC 6376 
dig +short mandrill._domainkey.ui.com TXT
Check DKIM key for selector 'zendesk1' RFC 6376 
dig +short zendesk1._domainkey.ui.com TXT
Check DKIM key for selector 'zendesk2' RFC 6376 
dig +short zendesk2._domainkey.ui.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 18.172.134.102 (Team Cymru) 
dig +short 102.134.172.18.origin.asn.cymru.com TXT
ASN lookup for 18.172.134.21 (Team Cymru) 
dig +short 21.134.172.18.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 consistent · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Consistent 15107 runs
DKIM
Consistent 14884 runs
DMARC
Consistent 15088 runs
DANE/TLSA
Consistent 14866 runs
DNSSEC
Consistent 15065 runs
BIMI
Consistent 14881 runs
MTA-STS
Consistent 14902 runs
TLS-RPT
Consistent 14917 runs
CAA
Consistent 14914 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 ui.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer ui.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer ui.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer ui.com NS
Query TXT records (RFC 1035) 
dig +noall +answer ui.com TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short ui.com TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.ui.com TXT
Check DKIM key for selector 'google' (RFC 6376) 
dig +short google._domainkey.ui.com TXT
Check DKIM key for selector 'k2' (RFC 6376) 
dig +short k2._domainkey.ui.com TXT
Check DKIM key for selector 'k3' (RFC 6376) 
dig +short k3._domainkey.ui.com TXT
Check DKIM key for selector 'mandrill' (RFC 6376) 
dig +short mandrill._domainkey.ui.com TXT
Check DKIM key for selector 'zendesk1' (RFC 6376) 
dig +short zendesk1._domainkey.ui.com TXT
Check DKIM key for selector 'zendesk2' (RFC 6376) 
dig +short zendesk2._domainkey.ui.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 18.172.134.102 (Team Cymru) 
dig +short 102.134.172.18.origin.asn.cymru.com TXT
ASN lookup for 18.172.134.21 (Team Cymru) 
dig +short 21.134.172.18.origin.asn.cymru.com TXT

0s

Running Real-Time Scan Telemetry

Most scans complete in less than one minute. Some may take longer.

Markers represent known resolver locations. Anycast routing selects the nearest node — exact routing is internal to each provider.

Pipeline nodes reflect live data as each analysis phase completes.

Telemetry Log 0 polls