Hostname
admin.foundationcenter.org
Last fetched
admin.foundationcenter.org resolves to 99.84.203.109, announced in 99.84.200.0/21 by AMAZON-02 - Amazon.com, Inc. in US. admin.foundationcenter.org is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 99.84.203.109
99.84.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Minneapolis, US
- 99.84.203.50
99.84.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Minneapolis, US
- 99.84.203.55
99.84.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Minneapolis, US
- 99.84.203.80
99.84.200.0/21 · AMAZON-02 - Amazon.com, Inc. · Minneapolis, US
- 99.84.215.114
99.84.214.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.215.35
99.84.214.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.215.79
99.84.214.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
- 99.84.215.9
99.84.214.0/23 · AMAZON-02 - Amazon.com, Inc. · Los Angeles, US
IPv6 resolution
No AAAA record for admin.foundationcenter.org is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for admin.foundationcenter.org. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Mail and authentication
Nameservers
- ns-241.awsdns-30.com
- ns-1004.awsdns-61.net
- ns-1202.awsdns-22.org
- ns-1894.awsdns-44.co.uk
MX records
- foundationcenter-org.mail.protection.outlook.com
SPF policy
- include: spf.mandrillapp.com
- include: mailsenders.netsuite.com
- include: spf.protection.outlook.com
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from admin.foundationcenter.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: "admin.foundationcenter.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.