Skip to content

Hostname

sfenvironment.org

Last fetched

sfenvironment.org resolves to 104.21.52.151, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. sfenvironment.org is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · sfenvironment.orgRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/sfenvironment.org

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:2
Registrant organisation
greg elin
Contact emails
0466307abab2b6da80ffd02447007913-1831323@contact.gandi.net, 0f23b5c2f47f2efa249cd2e126c838f7-1831323@contact.gandi.net, 26eb41e71c4309aa147a7d265e60cbc9-1831323@contact.gandi.net, 3317552331a978b190209d522a8a37a1-1831323@contact.gandi.net

Subdomains

Subdomain
antibiotics.sfenvironment.org
commission.sfenvironment.org
dev.sfenvironment.org
files.sfenvironment.org
oldsite.sfenvironment.org
plan.sfenvironment.org
signmaker.sfenvironment.org
stage.sfenvironment.org
warehouse.sfenvironment.org
www.sfenvironment.org

Showing 10 of 10 subdomains (10 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • luke.ns.cloudflare.com
  • sunny.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com
  • route1.mx.cloudflare.net
  • route2.mx.cloudflare.net
  • route3.mx.cloudflare.net

SPF policy

  • include: _spf.mx.cloudflare.net

Threat-feed evidence

History

Related pages

Pivot from sfenvironment.org into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "sfenvironment.org"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.