generated: '2026-08-29'
method: probed
source: live DNS/TLS/HTTP probes of the company's own domain (viridos.com), 2026-08-29
note: >-
  The first automated run of probe-domain-security.py profiled forgeglobal.com, because the only
  host named anywhere in apis.yml was a Forge Global secondary-market listing page. Forge Global is
  a trading venue, not Viridos, so that result has been replaced with a probe of the company's own
  domain. DNS and mail for viridos.com are still fully configured and enterprise-grade, but no web
  vhost is served: every HTTP path returns "403 | Access blocked" from a SiteGround default vhost,
  behind a certificate issued for giowm1252.siteground.biz rather than for viridos.com.
hosts:
- host: viridos.com
  https: false
  https_note: >-
    TLS handshake succeeds (TLSv1.3, TLS_AES_256_GCM_SHA384) but the certificate does not cover
    viridos.com - subject CN=giowm1252.siteground.biz, issuer Let's Encrypt, valid
    2026-06-29 to 2026-09-27 - so a verifying client fails with a name mismatch.
  tls_version: TLSv1.3
  cert_subject: CN=giowm1252.siteground.biz
  cert_issuer: "C=US, O=Let's Encrypt, CN=YR1"
  cert_expires: Sep 27 07:42:30 2026 GMT
  cert_covers_host: false
  http_status: 403
  http_body: '403 | Access blocked'
  response_headers:
    server: nginx
    sg-captcha: challenge
    x-robots-tag: noindex
    x-default-vhost: '1'
  hsts: null
  hsts_note: no Strict-Transport-Security header is returned; the host serves no site to protect
domains:
- domain: viridos.com
  a_records:
  - 35.208.4.74
  nameservers:
  - dns1.easydns.com
  - dns2.easydns.net
  - dns3.easydns.ca
  dnssec: false
  dnssec_evidence: no DS record at the parent and no RRSIG on the A response
  caa: []
  caa_note: no CAA record published, so any CA may issue for this domain
  spf: true
  spf_record: >-
    v=spf1 include:spf.protection.outlook.com include:us._netblocks.mimecast.com
    include:spfus.rocketseed.com include:_spf.atlassian.net include:_spf.psm.knowbe4.com -all
  spf_policy: '-all'
  dmarc: true
  dmarc_policy: reject
  dmarc_record: >-
    v=DMARC1; p=reject; fo=1; rua=mailto:REDACTED@rep.dmarcanalyzer.com;
    ruf=mailto:REDACTED@for.dmarcanalyzer.com;
  mx:
  - 10 us-smtp-inbound-1.mimecast.com
  - 20 us-smtp-inbound-2.mimecast.com
  observation: >-
    Mail posture is strong and still live - Mimecast inbound gateways, Microsoft 365 sending,
    SPF hard-fail, DMARC p=reject with aggregate and forensic reporting - while the web presence
    is gone entirely. This is the fingerprint of a wound-down company whose DNS and mail tenancy
    outlived its website.
- domain: dspace.bio
  note: >-
    The public demo host named in the company's own sgidspace README. Still resolves to AWS
    CloudFront (13.32.241.0/24) but every path returns 403; the distribution no longer serves
    the D-SPACE demo.
  a_records:
  - 13.32.241.2
  - 13.32.241.16
  - 13.32.241.38
  - 13.32.241.117
  http_status: 403