generated: '2026-08-26' method: probed source: dig + TCP/TLS probes against pavilion.io (2026-08-26) note: >- Pavilion Data Systems ceased operations on 2022-10-12. The registrable domain pavilion.io is still registered (GoDaddy, registry expiry 2027-01-29) and its DNS zone still answers, but no web server is listening: both A records (44.224.211.240, 44.224.118.103, AWS us-west-2) refuse connections on TCP 80 and 443. Mail records are still published, so the DNS-layer findings below are real and current while the HTTPS-layer findings are "host unreachable", not "misconfigured". hosts: - host: pavilion.io registrable_domain: pavilion.io dns: a: - 44.224.211.240 - 44.224.118.103 ns: - ns11.domaincontrol.com - ns12.domaincontrol.com mx: - aspmx.l.google.com - alt1.aspmx.l.google.com - alt2.aspmx.l.google.com - alt3.aspmx.l.google.com - alt4.aspmx.l.google.com https: reachable: false tcp_443: refused tcp_80: refused tls_version: null cert_expires: null observed: 'curl exit 28 / connection timed out; nc reports 80 and 443 closed on both A records' hsts: present: null note: not observable — no HTTPS response to read a Strict-Transport-Security header from dnssec: enabled: false dnskey_records: 0 ds_records: 0 caa: present: false records: [] spf: present: true record: 'v=spf1 include:_spf.google.com include:mktomail.com include:aspmx.pardot.com include:_spf.salesforce.com ~all' policy: '~all (softfail)' dmarc: present: true record: 'v=DMARC1; p=quarantine; rua=mailto:spoof-quarantine@pavilion.io; ruf=mailto:spoof-quarantine@pavilion.io; pct=100; ri=86400; fo=1;' policy: quarantine other_txt: - 'google-site-verification=-T8MX4jHcfmPdsfymazgoRCQhB0GZ_Am2ci2a7F_88I' - 'google-site-verification=l6913O0oxPbk793YcDQ2wHzWfb0qUhqKc2q49Bop-ek' - 'ZOOM_verify_d7ctiSHOSp2Hp0ly6-FXsg' registrar: name: GoDaddy.com, LLC creation_date: '2016-01-29' registry_expiry_date: '2027-01-29' last_updated: '2026-08-12'