Skip to content

Hostname

fostercity.org

Last fetched

fostercity.org resolves to 104.18.28.100, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. fostercity.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 · fostercity.orgRouting diversity3.0/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/fostercity.org

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
city of foster city
Contact emails
webmaster@fostercity.org

Subdomains

Subdomain
autodiscover.fostercity.org
bart.fostercity.org
citydocs.fostercity.org
client.fostercity.org
connect.fostercity.org
documents.fostercity.org
f1.fostercity.org
fcy-router.fostercity.org
helpdesk.fostercity.org
irlp.fostercity.org
lenny.fostercity.org
link.fostercity.org

Showing 12 of 27. View all subdomains →

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

  • laura.ns.cloudflare.com
  • micah.ns.cloudflare.com
  • ns45.domaincontrol.com
  • ns46.domaincontrol.com

MX records

  • d136844a.ess.barracudanetworks.com
  • d136844b.ess.barracudanetworks.com

SPF policy

  • include: spf.ess.barracudanetworks.com
  • include: spf-westus.emailsignatures365.com
  • include: spf.protection.outlook.com
  • include: _spf.teamaha.com
  • include: servers.mcsv.net
  • a: fostercity.org
  • mx: fostercity.org
  • ip: 209.234.105.8

Threat-feed evidence

History

Related pages

Pivot from fostercity.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: "fostercity.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.