Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 2 Apr 2026, 14:36 UTC
Duration 17.0s
Version v26.40.31
Integrity 6b40ab6422211292a9e14deb9e2aac6fe4e8ea9c40a77a7c79db69f8d082d4066e77cdd7319e48f5962b2c4543ea98fb60c06dcf8d0a7831e711c89804e58aea
Subject Domain
squareup.com

Engineer's DNS Intelligence Report

squareup.com
2 Apr 2026, 14:36 UTC · 17.0s ·v26.40.31 · SHA-3-512: 6b40✱✱✱✱ Verify ·Cross-Referenced
Executive Topology
Recon Mode Snapshot Re-analyze New Domain
Footprint Amazon Route 53 Google Workspace 14 SaaS Services
DNS Security & Trust Posture
Risk Level: Low Risk
3 protocols configured, 5 not configured, 1 unavailable on provider Why we go beyond letter grades
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 65% Currency 66/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 3 record types (A record at 18s), 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
SOA 21570s 1 hour (3600s) high SOA TTL is above typical — observed 21570s, 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.
MX 39s 1 hour (3600s) high MX TTL is below typical — observed 39s, 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 18s 1 hour (3600s) high A TTL is below typical — observed 18s, 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 30s 1 hour (3600s) high TXT TTL is below typical — observed 30s, 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 100s 1 day (86400s) high NS TTL is below typical — observed 100s, 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.

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 squareup.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-1248.awsdns-28.org
Serial 1
Admin ops+dns.squareup.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 31.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
Not Setup
DNS Tampering
Enterprise
Certificate Control
Open
Configured
SPF, DMARC (reject), DKIM
Not Configured
MTA-STS, TLS-RPT, BIMI, DNSSEC, CAA
Unavailable on Provider
DANE
Priority Actions 5 total Achievable posture: Secure
Medium Enable DNSSEC

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

RFC 4035
Low Add BIMI Record

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

BIMI displays your verified brand logo next to your emails in supporting mail clients.
TypeTXT
Hostdefault._bimi.squareup.com (BIMI default record)
Valuev=BIMI1; l=https://squareup.com/brand/logo.svg
RFC 9495
Low Add CAA Records

CAA records specify which Certificate Authorities may issue certificates for your domain, reducing the risk of unauthorized certificate issuance.

CAA constrains which CAs can issue certificates for this domain.
TypeCAA
Hostsquareup.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.squareup.com (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@squareup.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.squareup.com (MTA-STS policy record)
Valuev=STSv1; id=squareup.com
RFC 8461
Open Remediation Workspace — Copy-Paste Ready Records
Registrar (RDAP) OBSERVED LIVE
CSC Corporate Domains, Inc.
Where domain was purchased
Email Service Provider
Google Workspace
Strongly Protected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Amazon Route 53 Enterprise
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 3/10 lookups

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

v=spf1 include:squareup.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:stspg-customer.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 reject: the strongest compatible security stance, aligned with CISA and RFC guidance.

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

DKIM Records RFC 6376 §3.6 Consistent

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

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

DKIM key management delegated — _domainkey.squareup.com NS records point to an external service (ns.vali.email). DKIM selectors are dynamically managed and may include keys for services beyond what static scanning discovers.
k1._domainkey MailChimp 2048-bit Adequate
k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;
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
s1._domainkey SendGrid 2048-bit Adequate
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyQ5fOs4sKWihhSfyMnnp4BwwLk1fUON4PGZ6fVo/+6K3CwWBKkuXuAPmhThHEgOBMlgKdSrSb7WLyoGmPRIVzCUoioF+5jG7mIT4vuB/QV+0n0g5rdzOiTjJWgYrT5Y0uANdPss3qiPW+hR9VIUuDARADyyUCqTPczbrDYH7l1a+KK0wn/4M7GQc/ZJMyc7Gbe9OIrK/5Q5K13pPHF61bf/6YiqrqFb2cLGonRYZ6+vYfUwz0r9qToRoLoBOkNhScN9l8QC0x56ELHjDjXiG8gEUXNZUa+Zdm3UT800WYPStEIC+RQNSVGnYRKaVCCe0djGTZISM11stCtrtOn5kywIDAQAB
s2._domainkey SendGrid 2048-bit Adequate
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDOkeDbSu/ObfVBCLRXSBo5pmFuqF3it1r7qCBMSStYEPHzysnItO9qaKECUF0/Uljb7kXg00RtCH+RWriAogDfa4ZeIKcUY7oSHTbLTx2H7hV0I5inx1Qws0RQmAHMJcaWIdRMd4YStAbWhZd36I5KC45dCQz6PvsW7/qYKX4xYwIDAQAB
s3._domainkey Google Workspace (inferred) 2048-bit Adequate
k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2JrR8I6GyD12WpCI67ZIKbjbeQ8BsuWmMMzN+wRMd5YD54ceVyg2tP4WL1OyVe6aHHPCCheWLMAoQAr+d9qa/Mcs2eMnwS+iSvIivQRQk8vIAzcmc9tzjGu3UdXRjo/yAu4597/E376M4+xRA5bTJNKjYoHd0etLBnxWGzM9+zhkid9RqbQAX/8i3ajdpIMmEQzgyHFVMagivGC5qhVgcyMcGXGSX1jN04iSY/JYVGow6O/TlQtnBYlYmVCHziCHKuLDpf2MeooBXyC9HqYrkz00Hz8ACStkAG2mEfFUL/iUCGwK4TQgpOxY0vnNwB4AnqSSim9VUCP1Egu4ujF7zQIDAQAB
smtp._domainkey Google Workspace (inferred) 2048-bit Adequate
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDhef96Kr24I/GVyljeKYp7DzGH4DjsvNfejcvz0rq4CDXkgDmyreTTb6700jXQQt6kza2I89ZgGYQxCpavru42tUBmhXSq2qlL0fmr97sg8WP/u041ESZYtCW5Z5XJIPPN4lqO/UOqhHUEmCRBpZeiKf2rwNkaNGP1wzMtBgm6TwIDAQAB
square._domainkey Square Online 2048-bit Adequate
v=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCCcybvmWfnscoyXw6ptzHFLh65ZQvvhZtI6dmfGQD78rzfx2XHeZcW8o8nATp9HPeC2e3t5ZuMHbVNaOXjmphZ34+VEHFqnpJoPSBaj9Diz9J1dV26bggay6iTw9mGS6uOdbdNj9pdLEHBcFPbHJgbbcXbso3qf7Q1RFYxw7KegwIDAQAB
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

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
vali.email Authorized v=DMARC1;
datafeeds.phishlabs.com Authorized v=DMARC1
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? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3), but no BIMI brand verification and no CAA certificate restriction (RFC 8659) — visual impersonation via lookalike domains and unrestricted certificate issuance remain open vectors

BIMI BIMI Spec Consistent Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

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? No RFC 9116

No security.txt found

A security.txt file at /.well-known/security.txt provides security researchers with a standardized way to report vulnerabilities. See securitytxt.org for a generator.
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? Yes

AI governance signals observed

llms.txt llmstxt.org
Is this domain publishing AI-readable brand context? Yes
llms.txt found — domain provides structured context for LLMs View llms.txt
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 (2 items)
TypeDetailSeverityConfidence
llms_txt_found llms.txt file found providing structured LLM context info Observed
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 ns-1248.awsdns-28.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-1248.awsdns-28.org, ns-311.awsdns-38.com, ns-810.awsdns-37.net, ns-1816.awsdns-35.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-1248.awsdns-28.org No N/A N/A OK
ns-1816.awsdns-35.co.uk No N/A N/A OK
ns-311.awsdns-38.com No N/A N/A OK
ns-810.awsdns-37.net No N/A N/A OK

NS TTL Comparison Drift

Child TTL: 900s Drift: 0s

SOA Serial Consistency Consistent

ns-1248.awsdns-28.org: 1
ns-1816.awsdns-35.co.uk: 1
ns-311.awsdns-38.com: 1
ns-810.awsdns-37.net: 1
Nameserver Fleet Matrix Healthy

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

Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial
ns-1248.awsdns-28.org 205.251.196.224 2600:9000:5304:e000::1 AS16509
Amazon.com, Inc. 		1
ns-1816.awsdns-35.co.uk 205.251.199.24 2600:9000:5307:1800::1 AS16509
Amazon.com, Inc. 		1
ns-810.awsdns-37.net 205.251.195.42 2600:9000:5303:2a00::1 AS16509
Amazon.com, Inc. 		1
ns-311.awsdns-38.com 205.251.193.55 2600:9000:5301:3700::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

All 3 server(s) verified: encrypted transport confirmed via direct SMTP probe and DNS policy

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
MX Host STARTTLS TLS Version Cipher Certificate
aspmx.l.google.com TLSv1.3 TLS_AES_128_GCM_SHA256 Valid
Expires: 2026-06-01 (59 days)
Issuer: Google Trust Services
alt1.aspmx.l.google.com TLSv1.3 TLS_AES_128_GCM_SHA256 Valid
Expires: 2026-06-08 (66 days)
Issuer: Google Trust Services
aspmx4.googlemail.com TLSv1.3 TLS_AES_128_GCM_SHA256 Valid
Expires: 2026-06-01 (59 days)
Issuer: Google Trust Services
Multi-Vantage Probe Results
Unanimous: TLS verified 2 probes, 1 responded
US-East (Boston) observed
All servers support TLS
France - EU skipped
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
AS13335 Cloudflare, Inc. US
IPv4 Mappings:
162.159.136.66 → AS13335 (162.159.128.0/19)
162.159.137.66 → AS13335 (162.159.128.0/19)

Edge / CDN Success Cloudflare

Domain is served through Cloudflare

Behind CDN Origin Hidden
ASN 13335 is Cloudflare

SaaS TXT Footprint Success 14 services

Detected 14 SaaS 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
Stripe stripe-verification=65D5F85D03979AEEF3452A27D1EFACD75E9D04DCC44E1BC99F4EBBCFCB7F8F26
Apple apple-domain-verification=sRlD9NsdK27SFZHX
Google google-site-verification=Pqbi42Git5I6oJ6ShnRd4aUd2umxUHL5JAKHf_kSQwQ
Facebook facebook-domain-verification=cx3tov4g02lrdyzawmw6zfl8zgrc5c
Miro miro-verification=eb2231722e9ee6e925e69e31c221403361bbc1cb
Pinterest pinterest-site-verification=0fef3763fa30d8b29fca02b8d1e77626
Atlassian atlassian-domain-verification=9iYUpJGNkg1t97CI3rPIi2JSZhPPPq2vqa29bn1XafOtu0579nFxEzSX3VzIvcRm
GitHub _github-challenge-squareup.squareup.com.=7725774663
Statuspage status-page-domain-verification=75bhj6n7cwrd
Postman postman-domain-verification=a3440d0a55ffe5831bf45b9bb5136601ebf884dd1cb5a755daaa73104b1f682d6d88d0a4741b6eef6a33b6d69f18...
Microsoft MS=ms66034408
DocuSign docusign=60c2f7db-b230-4b3d-91be-06a59569d253
1Password 1password-site-verification=DREX2J7TXBEY5FGM2RYXBK366U
Smartsheet smartsheet-site-validation=W_x3SnUQHna2UrcNnqg-4GMu73nsWryz
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-1248.awsdns-28.org ns-1816.awsdns-35.co.uk ns-311.awsdns-38.com ns-810.awsdns-37.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 (1 difference found)
Resolver Differences:
TXT: OpenDNS returned different results: [MS=ms66034408 NRZYY _ek1nrewwbsrikaiet5cox7909jno0th asv=2196a8f94eda64bc9d0abd83d4b93284 ca3-2cc3579a5da949a0bd2bc349e2b82c52 ca3-37fc58abdd5a4cf8ab5e8893db8298be ca3-4725c4c959644520b1df50805f72dca7 ca3-52a6dd26ecd1423ca816dac4d4b00678 ca3-60ed3ea4c1e141c79e4715175c4342f3 ca3-61da443be93c4975accb29e3bbf89560 ca3-6a7c53b6aded4260a698de411a9640b8]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

162.159.136.66
162.159.137.66
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

30 aspmx4.googlemail.com.
10 aspmx.l.google.com.
20 alt1.aspmx.l.google.com.
30 aspmx5.googlemail.com.
30 aspmx3.googlemail.com.
20 alt2.aspmx.l.google.com.
30 aspmx2.googlemail.com.
Priority + mail server for email delivery
Google Workspace

SRVServices

_xmpp-client._tcp: 20 0 5222 talk4.l.google.com.
_xmpp-client._tcp: 20 0 5222 talk2.l.google.com.
_xmpp-client._tcp: 20 0 5222 talk1.l.google.com.
_xmpp-client._tcp: 5 0 5222 talk.l.google.com.
_xmpp-client._tcp: 20 0 5222 talk3.l.google.com.
SIP, XMPP, or other service endpoints
Web: Reachable (2 IPv4, 0 IPv6) Mail: 7 servers Services: 5 endpoints
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 133 subdomains discovered
How did we find these?
CT logs unavailable 133 current 0 expired 5 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)
account.squareup.com CT Log Current — 8 2025-07-22T00:00:00Z
acs.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
admin.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
amazon-dxcon-fgcpnxiq.squareup.com CT Log Current — — — —
amazon-dxcon-fgl1m5va.squareup.com CT Log Current — — — —
amazon-dxvif-fghwxbo3.squareup.com CT Log Current — — — —
amazon-dxvif-fhcurqt1.squareup.com CT Log Current — — — —
amex-api.squareup.com CT Log Current — 4 2026-01-18T02:08:42Z
amex.3ds.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
api-au.squareup.com CT Log Current — 16 2025-07-22T00:00:00Z
api-felica.squareup.com CT Log Current — 9 2025-03-03T13:25:19Z
api-global.iad1.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
api-global.squareup.com CT Log Current — 10 2025-07-22T00:00:00Z
api-jp.nrt1.squareup.com CT Log Current — 1 2026-01-26T00:00:00Z
api-jp.squareup.com CT Log Current — 7 2026-01-16T21:23:48Z
api.broadway.squareup.com CT Log Current — — — —
api.iad1.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
api.nrt1.squareup.com CT Log Current — 1 2026-01-26T00:00:00Z
api.sjc1.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
api.squareup.com CT Log Current — 10 2026-01-13T00:00:00Z
app.squareup.com CT Log Current — 8 2025-07-22T00:00:00Z
apsales.squareup.com CT Log Current — 2 2026-01-02T21:04:57Z
atlas.squareup.com CT Log Current — 4 2025-07-22T00:00:00Z
balances.squareup.com CT Log Current — 1 2025-07-10T00:00:00Z
block-ca.squareup.com CT Log Current — 2 2025-04-08T00:00:00Z
block-oidc.squareup.com CT Log Current — 1 2025-05-24T00:00:00Z
blog.squareup.com CT Log Current — 10 2025-06-30T02:24:20Z
book.squareup.com CT Log Current — 8 2025-07-22T00:00:00Z
brand.squareup.com CT Log Current — 10 2025-06-30T02:24:20Z
broadway.squareup.com CT Log Current — 18 2025-06-18T00:00:00Z
buyer-portal.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
calendar.squareup.com DNS Current ghs.google.com — — —
canary-fastly.squareup.com CT Log Current — 1 2026-02-04T05:13:01Z
canary-one.squareup.com CT Log Current — 4 2026-01-16T03:40:51Z
capi.squareup.com CT Log Current — 1 2026-02-14T14:38:15Z
capital.squareup.com CT Log Current — 8 2025-07-22T00:00:00Z
careers-origin.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
careers.squareup.com CT Log Current — 9 2025-06-30T02:24:20Z
cdn.app.squareup.com CT Log Current — — — —
cf.api-global.squareup.com CT Log Current — 2 2026-02-11T21:01:15Z
cf.api-jp.squareup.com CT Log Current — 2 2026-02-11T21:01:00Z
cf.api.squareup.com CT Log Current — 2 2026-02-11T21:00:01Z
cf.app.squareup.com CT Log Current — 2 2026-02-11T21:01:56Z
community.squareup.com CT Log Current — 2 2026-02-27T00:10:24Z
connect.squareup.com CT Log Current — 12 2026-01-12T20:25:36Z
content-platforms.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
corner-move.squareup.com CT Log Current — 9 2025-06-30T02:24:20Z
corner.squareup.com CT Log Current — 1 2025-08-09T00:00:00Z
design.squareup.com CT Log Current — 9 2025-06-30T02:24:20Z
developer.squareup.com CT Log Current — 7 2025-06-30T02:24:20Z
developers.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
discover.3ds.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
docs.connect.squareup.com CT Log Current — 4 2025-07-22T00:00:00Z
docs.squareup.com DNS Current ghs.google.com — — —
edgecanary-blue.squareup.com CT Log Current — 4 2026-01-21T19:56:52Z
edgecanary.squareup.com CT Log Current — 4 2026-01-20T17:24:42Z
engage.squareup.com CT Log Current — 4 2026-03-01T18:13:33Z
enterprise.squareup.com CT Log Current — 5 2026-01-27T17:52:21Z
escheatment.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
explorer-gateway.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
fallback.community.squareup.com CT Log Current — 6 2026-01-03T03:14:47Z
ftps.p.iad1.squareup.com CT Log Current — 3 2025-04-17T00:00:00Z
ftps.p.sjc1.squareup.com CT Log Current — 3 2025-04-17T00:00:00Z
ftps.p.sjc1b.squareup.com CT Log Current — 3 2025-04-17T00:00:00Z
ftps.p.squareup.com CT Log Current — 3 2025-04-17T00:00:00Z
fulfillment-ups.squareup.com CT Log Current — 1 2025-05-12T00:00:00Z
fulfillment.squareup.com CT Log Current — 9 2025-06-30T02:24:20Z
ge-1-0-4-0.br01.365.corp.squareup.com CT Log Current — — — —
ge-1-0-4-0.br02.365.corp.squareup.com CT Log Current — — — —
ge-1-1-6-0.br02.365.corp.squareup.com CT Log Current — — — —
harrisli-dev-cf.squareup.com CT Log Current — 8 2026-01-12T19:53:55Z
hc-c.squareup.com CT Log Current — 4 2026-01-09T14:13:01Z
hc-f.squareup.com CT Log Current — 2 2026-01-17T11:42:37Z
help.p.sjc1.squareup.com CT Log Current — 2 2026-01-20T00:00:00Z
help.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
ht.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
images.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
imagestest.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
inbox.squareup.com CT Log Current — 4 2026-01-07T17:41:09Z
investors.squareup.com CT Log Current — 2 2026-01-10T03:27:59Z
it-portal.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
jcb.3ds.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
jobs.squareup.com CT Log Current — 10 2025-06-30T02:24:20Z
js.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
lo0-0.br02.365.corp.squareup.com CT Log Current — — — —
localizer.squareup.com CT Log Current — 9 2025-06-30T02:24:20Z
localoffers.squareup.com CT Log Current — 8 2025-07-22T00:00:00Z
mail.squareup.com DNS Current ghs.google.com — — —
mailbox.squareup.com CT Log Current — 3 2025-04-17T00:00:00Z
mastercard.3ds.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
mcp.squareup.com CT Log Current — 4 2026-02-19T17:42:31Z
mobile-releases-staging.squareup.com CT Log Current — 1 2025-08-20T00:00:00Z
mobile-releases.squareup.com CT Log Current — 1 2025-08-20T00:00:00Z
my.squareup.com CT Log Current — 8 2025-07-22T00:00:00Z
nat.st.sjc1.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
new-hire-hub.squareup.com CT Log Current — 4 2025-07-22T00:00:00Z
newhire-portal.squareup.com CT Log Current — 4 2025-07-22T00:00:00Z
non-disclosure.corp.squareup.com CT Log Current — 1 2025-08-18T00:00:00Z
ocr-connect.squareup.com CT Log Current — 9 2025-06-30T02:24:20Z
origin-api-jp.squareup.com CT Log Current — 1 2026-01-26T00:00:00Z
origin-careers.squareup.com CT Log Current — 9 2025-06-30T02:24:20Z
origin-jp.squareup.com CT Log Current — 1 2026-01-26T00:00:00Z
origin.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
pci-connect.squareup.com CT Log Current — 10 2026-01-13T00:00:00Z
privacy.squareup.com CT Log Current — 9 2025-06-30T02:24:20Z
profile.squareup.com CT Log Current — 6 2026-01-13T01:26:22Z
restaurants.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
rsvpify.events.squareup.com CT Log Current — 2 2026-01-26T23:29:21Z
rsyslog-tls-staging.squareup.com CT Log Current — 3 2025-12-05T00:00:00Z
rsyslog-tls.squareup.com CT Log Current — 3 2025-12-10T00:00:00Z
sa.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
sc-connect.squareup.com CT Log Current — 9 2025-06-30T02:24:20Z
sdk.squareup.com CT Log Current — 2 2026-01-28T22:53:05Z
secrets-authority-staging.squareup.com CT Log Current — 3 2025-10-22T00:00:00Z
secrets-authority.squareup.com CT Log Current — 3 2025-10-22T00:00:00Z
sentry.squareup.com CT Log Current — 9 2025-06-30T02:24:20Z
shuttle.squareup.com CT Log Current — 1 2025-12-04T00:00:00Z
status.squareup.com DNS Current status.squareup.com.cdn.cloudflare.net — — —
store.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
supportprofile.squareup.com CT Log Current — 6 2025-07-22T00:00:00Z
switchboard.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
visa.3ds.squareup.com CT Log Current — 2 2025-07-22T00:00:00Z
vpn.squareup.com DNS Current vpn.corp.squareup.com — — —
www.community.squareup.com CT Log Current — 2 2026-02-27T00:10:24Z
www.ftps.p.squareup.com CT Log Current — 3 2025-04-17T00:00:00Z
www.squareup.com CT Log Current — 7 2025-06-30T02:24:20Z
xe-0-0-0-0.br01.365.corp.squareup.com CT Log Current — — — —
xe-0-0-0-0.br02.365.corp.squareup.com CT Log Current — — — —
xe-0-0-1-0.br01.365.corp.squareup.com CT Log Current — — — —
xe-0-0-1-0.br02.365.corp.squareup.com CT Log Current — — — —
xe-0-0-2-0.br01.365.corp.squareup.com CT Log Current — — — —
xe-0-0-3-0.br01.365.corp.squareup.com CT Log Current — — — —
xmstest.squareup.com CT Log Current — 4 2026-01-11T18:25:33Z
Export Recon (CSV)
Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.
DNS Intelligence What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records (Public DNS cache)
Authoritative Records (Source of truth)
A Synchronized 2 / 2 records
162.159.136.66
162.159.136.66
162.159.137.66
162.159.137.66
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 0 / 0 records
No records
No records
DMARC _dmarc.squareup.com RFC 7489 §6.3 1 / 0 records
v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email,mailto:postmasters@squareup.com,mailto:square-dmarc@datafeeds.phishlabs.com; ruf=mailto:dmarc-ruf@squareup.com,mailto:square-dmarc@datafeeds.phishlabs.com
—
MX RFC 5321 Synchronized 7 / 7 records
30 aspmx4.googlemail.com.
10 aspmx.l.google.com.
10 aspmx.l.google.com.
20 alt1.aspmx.l.google.com.
20 alt1.aspmx.l.google.com.
20 alt2.aspmx.l.google.com.
30 aspmx5.googlemail.com.
30 aspmx2.googlemail.com.
30 aspmx3.googlemail.com.
30 aspmx3.googlemail.com.
20 alt2.aspmx.l.google.com.
30 aspmx4.googlemail.com.
30 aspmx2.googlemail.com.
30 aspmx5.googlemail.com.
NS RFC 1035 Synchronized 4 / 4 records
ns-810.awsdns-37.net.
ns-1248.awsdns-28.org.
ns-1248.awsdns-28.org.
ns-1816.awsdns-35.co.uk.
ns-311.awsdns-38.com.
ns-311.awsdns-38.com.
ns-1816.awsdns-35.co.uk.
ns-810.awsdns-37.net.
SOA RFC 1035 Synchronized 1 / 1 records
ns-1248.awsdns-28.org. ops+dns.squareup.com. 1 7200 900 1209600 86400
ns-1248.awsdns-28.org. ops+dns.squareup.com. 1 7200 900 1209600 86400
TXT RFC 7208 §4 65 / 0 records
asv=2196a8f94eda64bc9d0abd83d4b93284
—
stripe-verification=65D5F85D03979AEEF3452A27D1EFACD75E9D04DCC44E1BC99F4EBBCFCB7F8F26
—
ca3-6a7c53b6aded4260a698de411a9640b8
—
logmein-verification-code=d29bfe7e-a479-4ca9-862a-c87f1072f273
—
elevenlabs=SBg1u4pIdlsVtIaiXt8QeVV3yNEzeNtNs51br5upR4g
—
ca3-37fc58abdd5a4cf8ab5e8893db8298be
—
ca3-2cc3579a5da949a0bd2bc349e2b82c52
—
lucidlink-verification=9W8003J10X2KM6X9SS663MSG08
—
NRZYY
—
ca3-e9926e04f8c148e89e7c600213cb986a
—
apple-domain-verification=sRlD9NsdK27SFZHX
—
ca3-4725c4c959644520b1df50805f72dca7
—
google-site-verification=Pqbi42Git5I6oJ6ShnRd4aUd2umxUHL5JAKHf_kSQwQ
—
atlassian-sending-domain-verification=e540d827-02ac-4946-acee-a77c1df352f6
—
facebook-domain-verification=cx3tov4g02lrdyzawmw6zfl8zgrc5c
—
v=spf1 include:squareup.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:stspg-customer.com ~all
—
drift-domain-verification=71b345a7ff662bf9535a86f2ddbb50016872b37a56c6988edd6c39542a3ccd68
—
bugcrowd-verification=2aa613d4e374f9460060422314f1098d
—
miro-verification=eb2231722e9ee6e925e69e31c221403361bbc1cb
—
google-site-verification=DsJnK_h3aiHyf-DRKaVdc_iNooeRxSGu8PqkY2KTd74
—
pinterest-site-verification=0fef3763fa30d8b29fca02b8d1e77626
—
loom-site-verification=0036b963640944f580e4c1fec45c8d9d
—
amp-by-sourcegraph-domain-verification-w953qg=xBRagiAevq79uusplKZZPSBsg
—
facebook-domain-verification=ddco927gzciui72ra27s2aq1301vjo
—
traction-guest=2bfeba2a-05af-4152-a3ab-93d855c8746f
—
atlassian-domain-verification=9iYUpJGNkg1t97CI3rPIi2JSZhPPPq2vqa29bn1XafOtu0579nFxEzSX3VzIvcRm
—
_github-challenge-squareup.squareup.com.=7725774663
—
ca3-a3666da4d1ec4264a8d59cb8616cf0ed
—
google-site-verification=UVRQgeyjSjLUSa6l8xBu1fNQBxxKOL85Pg4457B-oms
—
zapier-domain-verification-challenge=9b5ca019-06d3-40bb-a52b-915e42e1d884
—
parsec-domain-verification=td_2c0ZaSdVBfxDHQsb5HjmvQCHaKF
—
status-page-domain-verification=75bhj6n7cwrd
—
docker-verification=4ed46600-9205-400a-b12d-d0135704e9e9
—
pinterest-site-verification=49699bc2c694be95ffea5692960d72b4
—
anthropic-domain-verification-7xmqab=NeSCp0Pj0sOrdc5jJgJiOsHFb
—
ca3-8bbc566c4b4c4974950a83527517492d
—
onetrust-domain-verification=c01f4d184d3c4f2ba9503a4583e88101
—
onetrust-domain-verification=0c79435fab8d45ac85eb4ac5041ab282
—
ca3-60ed3ea4c1e141c79e4715175c4342f3
—
reachdesk-verification=IjVgh43q7kQHr9cSU6FYVjktOt6FNW6I1VKqC7cLSPXDW0hqMpa5pPjEJ39dnG99
—
postman-domain-verification=a3440d0a55ffe5831bf45b9bb5136601ebf884dd1cb5a755daaa73104b1f682d6d88d0a4741b6eef6a33b6d69f1856366a06433b7902f85bafb358ea854552f9
—
ca3-61da443be93c4975accb29e3bbf89560
—
VISA=2D3280EA528BCBDA893DA573CEFA72CE
—
stripe-verification=cfd5f1b3267861ed07fba1b121f0161da96c9fb30c97f590fc88db51506b4710
—
gitkraken-domain-verification=8e6bcedb6a5ded444186409140245b606ca0417109d394ee4e5b2b7df5e56ee0
—
ca3-bd8eae9a6ea245b68811b976990fc57d
—
notion_verify_3U}dr=+.N}vm0w.DoqiC%JJ}N0W5^}hnd1Wus9zb^EVJDw9pD%jG)hQ}V__qkd3U)4s!Xp
—
cursor-domain-verification-zvsqws=WAenirNPzeew2GcY4MKkAk41T
—
ca3-52a6dd26ecd1423ca816dac4d4b00678
—
MS=ms66034408
—
docusign=60c2f7db-b230-4b3d-91be-06a59569d253
—
google-site-verification=mlc7S_Dm5aPcPQjEe_Pj3GuiF9_svNtafsWw_kPeN48
—
stripe-verification=5a8a00371398aa2466b713faf14e6edc9140160c32f51d02067af5dcd8591cc8
—
google-site-verification=xoi3YhHkHmKwoyDO259v-DxMgY38xT08RNKMLTtTJ3A
—
ca3-c491f3300b6641e1b8a3104b693d7bb3
—
docusign=35ce9b6e-d74a-48ad-b437-690ad0602f81
—
_github-challenge-squareup.squareup.com=7725774663
—
_ek1nrewwbsrikaiet5cox7909jno0th
—
wiz-domain-verification=e401377ed0542bf72e67d32b62781795a75cfc1a84c18520e6263bfdf415cd0e
—
1password-site-verification=DREX2J7TXBEY5FGM2RYXBK366U
—
google-site-verification=OuiYXiYuWdfPSus7uBL6EhJawkg5BOERlvclE-QXVcs
—
smartsheet-site-validation=W_x3SnUQHna2UrcNnqg-4GMu73nsWryz
—
wrike-verification=MzIwNzgwMDo2MGE1NjUwYThkMmExMjkzZDg3MGVmMDE3MzkzMDJlOTE4YTY5YmZlMjNlZGE5MGY5MWMzODFhNTFmNDU5MTNi
—
google-site-verification=lIzmfEdVTz2PAEu4n8NckVPZhd-mQiGTlc0xBXlOhtU
—
ca3-a19f55866123448fb9e26ff3ed0d6d86
—
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.

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

Email Authentication

Check SPF record RFC 7208 
dig +short squareup.com TXT | grep -i spf
Check DMARC policy RFC 7489 
dig +short _dmarc.squareup.com TXT
Check DKIM key for selector 'k1' RFC 6376 
dig +short k1._domainkey.squareup.com TXT
Check DKIM key for selector 'k2' RFC 6376 
dig +short k2._domainkey.squareup.com TXT
Check DKIM key for selector 'k3' RFC 6376 
dig +short k3._domainkey.squareup.com TXT
Check DKIM key for selector 'mandrill' RFC 6376 
dig +short mandrill._domainkey.squareup.com TXT
Check DKIM key for selector 's1' RFC 6376 
dig +short s1._domainkey.squareup.com TXT
Check DKIM key for selector 's2' RFC 6376 
dig +short s2._domainkey.squareup.com TXT
Check DKIM key for selector 's3' RFC 6376 
dig +short s3._domainkey.squareup.com TXT
Check DKIM key for selector 'smtp' RFC 6376 
dig +short smtp._domainkey.squareup.com TXT
Check DKIM key for selector 'square' RFC 6376 
dig +short square._domainkey.squareup.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 162.159.136.66 (Team Cymru) 
dig +short 66.136.159.162.origin.asn.cymru.com TXT
ASN lookup for 162.159.137.66 (Team Cymru) 
dig +short 66.137.159.162.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 squareup.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer squareup.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer squareup.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer squareup.com NS
Query TXT records (RFC 1035) 
dig +noall +answer squareup.com TXT

Email Authentication

Check SPF record (RFC 7208) 
dig +short squareup.com TXT | grep -i spf
Check DMARC policy (RFC 7489) 
dig +short _dmarc.squareup.com TXT
Check DKIM key for selector 'k1' (RFC 6376) 
dig +short k1._domainkey.squareup.com TXT
Check DKIM key for selector 'k2' (RFC 6376) 
dig +short k2._domainkey.squareup.com TXT
Check DKIM key for selector 'k3' (RFC 6376) 
dig +short k3._domainkey.squareup.com TXT
Check DKIM key for selector 'mandrill' (RFC 6376) 
dig +short mandrill._domainkey.squareup.com TXT
Check DKIM key for selector 's1' (RFC 6376) 
dig +short s1._domainkey.squareup.com TXT
Check DKIM key for selector 's2' (RFC 6376) 
dig +short s2._domainkey.squareup.com TXT
Check DKIM key for selector 's3' (RFC 6376) 
dig +short s3._domainkey.squareup.com TXT
Check DKIM key for selector 'smtp' (RFC 6376) 
dig +short smtp._domainkey.squareup.com TXT
Check DKIM key for selector 'square' (RFC 6376) 
dig +short square._domainkey.squareup.com TXT

Domain Security

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

Transport Security

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

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

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

Transport Security

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

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 162.159.136.66 (Team Cymru) 
dig +short 66.136.159.162.origin.asn.cymru.com TXT
ASN lookup for 162.159.137.66 (Team Cymru) 
dig +short 66.137.159.162.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