Hostname
unifyfcu.com
Last fetched
unifyfcu.com resolves to 107.21.48.138, announced in 107.21.0.0/18 by AMAZON-AES - Amazon.com, Inc. in US. unifyfcu.com 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
- 107.21.48.138
107.21.0.0/18 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.211.65.219
18.208.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.232.217.231
34.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.193.170.93
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.73.198.145
52.72.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.86.245.16
54.86.0.0/16 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for unifyfcu.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns1-07.azure-dns.com
- ns1.sungardns.com
- ns2.sungardns.com
- ns3.sungardns.com
- ns4-07.azure-dns.info
- ns2-07.azure-dns.net
- ns3-07.azure-dns.org
MX records
- unifyfcu-com.mail.protection.outlook.com
SPF policy
- ip: 144.86.201.0/24
- ip: 4.17.224.0/24
- ip: 8.35.5.0/24
- ip: 144.86.200.0/26
- ip: 149.72.47.228/32
- ip: 139.131.126.26/32
- ip: 139.131.76.33/32
- ip: 173.239.115.34/32
- ip: 65.182.202.34/32
- ip: 98.158.81.61/32
- ip: 104.152.224.62/32
- ip: 139.131.76.85/32
- include: spf.infoimageinc.com
- exists: %{i}._spf.inkyphishfence.com
- include: spfref.jackhenry.com
- include: spf.mandrillapp.com
- include: spf.protection.outlook.com
- include: _spf.btbpo.net
- a: mailm.liveperson.net
- ip: 139.131.82.157
- ip: 173.239.115.45
- ip: 65.182.202.48
Threat-feed evidence
History
Related pages
Pivot from unifyfcu.com 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: "unifyfcu.com"})-[: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.